linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoph Hellwig <hch@infradead.org>,
	Andi Kleen <andi@firstfloor.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Quentin Barnes <qbarnes+nfs@yahoo-inc.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	Nick Piggin <npiggin@suse.de>,
	Steven Whitehouse <swhiteho@redhat.com>,
	David Howells <dhowells@redhat.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Jonathan Corbet <corbet@lwn.net>, Eric Paris <eparis@redhat.com>
Subject: Re: [RFC][PATCH v4] readahead: introduce O_RANDOM for POSIX_FADV_RANDOM
Date: Tue, 5 Jan 2010 10:45:33 +0800	[thread overview]
Message-ID: <20100105024533.GA30714@localhost> (raw)
In-Reply-To: <20100105132824.e6c0fb7f.sfr@canb.auug.org.au>

On Tue, Jan 05, 2010 at 10:28:24AM +0800, Stephen Rothwell wrote:
> Hi Fengguang,
> 
> On Tue, 5 Jan 2010 10:26:50 +0800 Wu Fengguang <fengguang.wu@intel.com> wrote:
> >
> > Where is it? I cannot grep find one in arch/.
> > There is one defined in include/asm-generic/fcntl.h:
> > 
> > #ifndef O_SYNC
> > #define __O_SYNC        04000000
> > #define O_SYNC          (__O_SYNC|O_DSYNC)
> > #endif
> > 
> > However it has one less '0' :)
> 
> Search for 0x800000 ...

Thanks, I got it..

Does that mean __O_SYNC would be _accidentally_ masked out in
__dentry_open() by the newly introduced fanotify bit?

        f->f_flags = (flags & ~(FMODE_EXEC | FMODE_NONOTIFY));

The above line is added in commit f67cee7b50b004357be383,
and can be fixed by the below patch.

Eric, what do you think?

Thanks,
Fengguang
---

 include/asm-generic/fcntl.h |    2 +-
 include/linux/fs.h          |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

--- linux.orig/include/asm-generic/fcntl.h	2010-01-05 10:42:36.000000000 +0800
+++ linux/include/asm-generic/fcntl.h	2010-01-05 10:42:57.000000000 +0800
@@ -5,7 +5,7 @@
 
 /*
  * FMODE_EXEC is 0x20
- * FMODE_NONOTIFY is 0x800000
+ * FMODE_NONOTIFY is 0x1000000
  * These cannot be used by userspace O_* until internal and external open
  * flags are split.
  * -Eric Paris
--- linux.orig/include/linux/fs.h	2010-01-05 10:40:33.000000000 +0800
+++ linux/include/linux/fs.h	2010-01-05 10:42:07.000000000 +0800
@@ -88,7 +88,7 @@ struct inodes_stat_t {
 #define FMODE_NOCMTIME		((__force fmode_t)2048)
 
 /* File was opened by fanotify and shouldn't generate fanotify events */
-#define FMODE_NONOTIFY		((__force fmode_t)8388608)
+#define FMODE_NONOTIFY		((__force fmode_t)0x1000000)
 
 /*
  * The below are the various read and write types that we support. Some of

  reply	other threads:[~2010-01-05  2:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091225000717.GA26949@yahoo-inc.com>
     [not found] ` <87aax18xms.fsf@basil.nowhere.org>
2009-12-30  5:15   ` [RFC][PATCH] Disabling read-ahead makes I/O of large reads small Wu Fengguang
2009-12-30  5:17     ` [RFC][PATCH 1/2] readahead: replace ra->mmap_miss with ra->flags Wu Fengguang
2009-12-30  5:24     ` [RFC][PATCH 2/2] readahead: avoid page-by-page reads on POSIX_FADV_RANDOM Wu Fengguang
2009-12-30 18:02       ` Andi Kleen
2009-12-31  1:39         ` Wu Fengguang
2009-12-31  2:53           ` Wu Fengguang
2009-12-31  3:03             ` Wu Fengguang
2009-12-31  4:31         ` [RFC][PATCH v2] readahead: introduce O_RANDOM_READ for POSIX_FADV_RANDOM Wu Fengguang
2010-01-08 13:08           ` Christoph Hellwig
2010-01-09 13:59             ` Wu Fengguang
2010-01-09 14:01               ` Wu Fengguang
2010-01-04  4:50         ` [RFC][PATCH v3] readahead: introduce O_RANDOM " Wu Fengguang
2010-01-04  5:17           ` Stephen Rothwell
2010-01-04  7:33             ` Christoph Hellwig
2010-01-04 12:56               ` [RFC][PATCH v4] " Wu Fengguang
2010-01-05  2:03                 ` Stephen Rothwell
2010-01-05  2:26                   ` Wu Fengguang
2010-01-05  2:28                     ` Stephen Rothwell
2010-01-05  2:45                       ` Wu Fengguang [this message]
2010-01-05  5:21                         ` Eric Paris
2010-01-05  3:18                       ` [RFC][PATCH v5] " Wu Fengguang
2010-01-05  3:27                         ` Wu Fengguang
2010-01-04 16:50               ` [RFC][PATCH v3] " Quentin Barnes
2010-01-04 18:57                 ` Andreas Dilger
2010-01-04  5:20           ` Minchan Kim
2010-01-04 12:16             ` Wu Fengguang
2010-01-05  1:46               ` Minchan Kim
2010-01-05  2:16                 ` Wu Fengguang
2010-01-05  3:40                   ` Minchan Kim

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=20100105024533.GA30714@localhost \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=corbet@lwn.net \
    --cc=dhowells@redhat.com \
    --cc=eparis@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=qbarnes+nfs@yahoo-inc.com \
    --cc=sfr@canb.auug.org.au \
    --cc=swhiteho@redhat.com \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).