From: Nathan Scott <nathans@sgi.com>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: [PATCH] remove broken direct I/O size ioctl
Date: Tue, 29 Nov 2005 09:43:57 +1100 [thread overview]
Message-ID: <20051129094357.G7047179@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <20051128222501.GA7238@lst.de>; from hch@lst.de on Mon, Nov 28, 2005 at 11:25:01PM +0100
On Mon, Nov 28, 2005 at 11:25:01PM +0100, Christoph Hellwig wrote:
> This ioctl tries to second guess direct I/O parameters which aren't
> a filesystem drivers business and shouldn't be exposed as an ioctl
> to start with.
Unfortunately there are some applications that will now start
to see errors from this ioctl if we go this route - whereas
before they would've been "functional", now they will break.
So, I think we need a different solution here. Yes, I agree
its a stupid call to have on Linux, but here we are, and apps
ported straight from IRIX have been made to use this.
cheers.
--
Nathan
prev parent reply other threads:[~2005-11-28 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 22:25 Christoph Hellwig
2005-11-28 22:43 ` Nathan Scott [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051129094357.G7047179@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®