linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: akpm@linux-foundation.org
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
	fengguang.wu@intel.com, davem@davemloft.net, hch@infradead.org,
	jamie@shareable.org, rdreier@cisco.com, schwab@linux-m68k.org,
	sfr@canb.auug.org.au
Subject: Re: [patch 4/6] vfs: O_* bit numbers uniqueness check
Date: Thu, 11 Mar 2010 18:11:04 -0500	[thread overview]
Message-ID: <1268349064.3768.3.camel@localhost> (raw)
In-Reply-To: <201003112211.o2BMBLfm013822@imap1.linux-foundation.org>

On Thu, 2010-03-11 at 14:11 -0800, akpm@linux-foundation.org wrote:
> From: Wu Fengguang <fengguang.wu@intel.com>
> 
> The O_* bit numbers are defined in 20+ arch/*, and can silently overlap. 
> Add a compile time check to ensure the uniqueness as suggested by David
> Miller.

Until the FMODE_ and O_ bits do not overload I think we need to check
FMODE_EXEC and FMODE_NONOTIFY (if you have that one) inside fcntl_init()
as well.  I guess I'll send a patch to someone ?Al? to add FMODE_EXEC to
the list....

-Eric

> 
> Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
> Cc: David Miller <davem@davemloft.net>
> Cc: Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
> Cc: Christoph Hellwig <hch@infradead.org>
> Cc: Eric Paris <eparis@redhat.com>
> Cc: Roland Dreier <rdreier@cisco.com>
> Cc: Jamie Lokier <jamie@shareable.org>
> Cc: Andreas Schwab <schwab@linux-m68k.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> 
>  fs/fcntl.c                  |   14 ++++++++++++--
>  include/asm-generic/fcntl.h |    2 ++
>  2 files changed, 14 insertions(+), 2 deletions(-)
> 
> diff -puN fs/fcntl.c~vfs-o_-bit-numbers-uniqueness-check fs/fcntl.c
> --- a/fs/fcntl.c~vfs-o_-bit-numbers-uniqueness-check
> +++ a/fs/fcntl.c
> @@ -739,11 +739,21 @@ void kill_fasync(struct fasync_struct **
>  }
>  EXPORT_SYMBOL(kill_fasync);
>  
> -static int __init fasync_init(void)
> +static int __init fcntl_init(void)
>  {
> +	/* please add new bits here to ensure allocation uniqueness */
> +	BUILD_BUG_ON(17 != HWEIGHT32(
> +		O_RDONLY	| O_WRONLY	| O_RDWR	|
> +		O_CREAT		| O_EXCL	| O_NOCTTY	|
> +		O_TRUNC		| O_APPEND	| O_NONBLOCK	|
> +		__O_SYNC	| O_DSYNC	| FASYNC	|
> +		O_DIRECT	| O_LARGEFILE	| O_DIRECTORY	|
> +		O_NOFOLLOW	| O_NOATIME	| O_CLOEXEC
> +		));
> +
>  	fasync_cache = kmem_cache_create("fasync_cache",
>  		sizeof(struct fasync_struct), 0, SLAB_PANIC, NULL);
>  	return 0;
>  }
>  
> -module_init(fasync_init)
> +module_init(fcntl_init)
> diff -puN include/asm-generic/fcntl.h~vfs-o_-bit-numbers-uniqueness-check include/asm-generic/fcntl.h
> --- a/include/asm-generic/fcntl.h~vfs-o_-bit-numbers-uniqueness-check
> +++ a/include/asm-generic/fcntl.h
> @@ -4,6 +4,8 @@
>  #include <linux/types.h>
>  
>  /*
> + * When introducing new O_* bits, please check its uniqueness in fcntl_init().
> + *
>   * FMODE_EXEC is 0x20
>   * FMODE_NONOTIFY is 0x1000000
>   * These cannot be used by userspace O_* until internal and external open
> _



  reply	other threads:[~2010-03-11 23:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 22:11 [patch 4/6] vfs: O_* bit numbers uniqueness check akpm
2010-03-11 23:11 ` Eric Paris [this message]
2010-03-12 13:41   ` [PATCH] vfs: O_* bit numbers uniqueness check fix Wu Fengguang
2010-03-12 15:01     ` Eric Paris
2010-03-12 15:14       ` Wu Fengguang
2010-03-12 15:15         ` Wu Fengguang
2010-03-12  0:39 ` [patch 4/6] vfs: O_* bit numbers uniqueness check Andreas Dilger
2010-03-12 13:42   ` [PATCH] vfs: O_* bit numbers uniqueness check fix 2 Wu Fengguang

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=1268349064.3768.3.camel@localhost \
    --to=eparis@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=fengguang.wu@intel.com \
    --cc=hch@infradead.org \
    --cc=jamie@shareable.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=rdreier@cisco.com \
    --cc=schwab@linux-m68k.org \
    --cc=sfr@canb.auug.org.au \
    --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).