From: Nathan Scott <nathans@sgi.com>
To: Marcelo Tosatti <marcelo@kvack.org>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: O_DIRECT, ext3fs, kernel 2.4.32... again
Date: Tue, 2 May 2006 07:28:08 +1000 [thread overview]
Message-ID: <20060502072808.A1873249@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <20060501112303.GA1951@DervishD>; from lkml@dervishd.net on Mon, May 01, 2006 at 01:23:03PM +0200
On Mon, May 01, 2006 at 01:23:03PM +0200, DervishD wrote:
> Hi Marcelo :)
>
> * Marcelo Tosatti <marcelo@kvack.org> dixit:
> > > Shouldn't ext3fs return an error when the O_DIRECT flag is
> > > used in the open call? Is the open call userspace only and thus
> > > only libc can return such error? Am I misunderstanding the entire
> > > issue and this is a perfectly legal behaviour (allowing the open,
> > > failing in the read operation)?
> >
> > Your interpretation is correct. It would be nicer for open() to
> > fail on fs'es which don't support O_DIRECT, but v2.4 makes such
> > check later at read/write unfortunately ;(
>
> Oops :(
Nothing else really make sense due to fcntl...
fcntl(fd, F_SETFL, O_DIRECT);
...can happen at any time, to enable/disable direct I/O.
cheers.
--
Nathan
next prev parent reply other threads:[~2006-05-01 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 6:32 DervishD
2006-05-01 6:20 ` Marcelo Tosatti
2006-05-01 11:23 ` DervishD
2006-05-01 21:28 ` Nathan Scott [this message]
2006-05-01 22:23 ` Bernd Eckenfels
2006-05-02 17:24 ` DervishD
2006-05-02 20:03 ` Nathan Scott
2006-05-03 5:27 ` DervishD
2006-05-03 6:35 ` Nathan Scott
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=20060502072808.A1873249@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@kvack.org \
/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®