From: Eric Dumazet <eric.dumazet@gmail.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Miller <davem@davemloft.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Al Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Eric Paris <eparis@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs: O_* bit numbers uniqueness check
Date: Wed, 06 Jan 2010 08:07:01 +0100 [thread overview]
Message-ID: <4B443695.5090301@gmail.com> (raw)
In-Reply-To: <20100106065526.GB11368@localhost>
Le 06/01/2010 07:55, Wu Fengguang a écrit :
> The O_* bit numbers are defined in 20+ arch/*, and hence can silently
> overlap. Add a boot time check to ensure the uniqueness as suggested
> by David Miller.
>
> 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>
> Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
> ---
> {
> + /* please add new bits here to ensure allocation uniqueness */
> + BUG_ON(20 != hweight32(
> + O_RDONLY | O_WRONLY | O_RDWR |
> + O_CREAT | O_EXCL | O_NOCTTY |
> + O_TRUNC | O_APPEND | O_NONBLOCK |
> + O_SYNC | FASYNC | O_DIRECT |
> + O_LARGEFILE | O_DIRECTORY | O_NOFOLLOW |
> + O_NOATIME | O_CLOEXEC | O_RANDOM |
> + FMODE_EXEC | FMODE_NONOTIFY));
> +
I cannot test it, but given O_RDONLY is 0, are you sure 20 bits are actually set ?
WARNING: multiple messages have this Message-ID (diff)
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Miller <davem@davemloft.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Al Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Eric Paris <eparis@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs: O_* bit numbers uniqueness check
Date: Wed, 06 Jan 2010 08:07:01 +0100 [thread overview]
Message-ID: <4B443695.5090301@gmail.com> (raw)
In-Reply-To: <20100106065526.GB11368@localhost>
Le 06/01/2010 07:55, Wu Fengguang a écrit :
> The O_* bit numbers are defined in 20+ arch/*, and hence can silently
> overlap. Add a boot time check to ensure the uniqueness as suggested
> by David Miller.
>
> 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>
> Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
> ---
> {
> + /* please add new bits here to ensure allocation uniqueness */
> + BUG_ON(20 != hweight32(
> + O_RDONLY | O_WRONLY | O_RDWR |
> + O_CREAT | O_EXCL | O_NOCTTY |
> + O_TRUNC | O_APPEND | O_NONBLOCK |
> + O_SYNC | FASYNC | O_DIRECT |
> + O_LARGEFILE | O_DIRECTORY | O_NOFOLLOW |
> + O_NOATIME | O_CLOEXEC | O_RANDOM |
> + FMODE_EXEC | FMODE_NONOTIFY));
> +
I cannot test it, but given O_RDONLY is 0, are you sure 20 bits are actually set ?
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-06 7:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 6:55 [PATCH] fs: O_* bit numbers uniqueness check Wu Fengguang
2010-01-06 7:07 ` Eric Dumazet [this message]
2010-01-06 7:07 ` Eric Dumazet
2010-01-06 7:20 ` Wu Fengguang
2010-01-06 9:13 ` Andreas Schwab
2010-01-09 13:33 ` Wu Fengguang
2010-01-09 13:33 ` Wu Fengguang
2010-01-06 7:08 ` Roland Dreier
2010-01-06 7:18 ` [PATCH v2] " Wu Fengguang
2010-01-06 7:30 ` Roland Dreier
2010-01-06 7:42 ` Wu Fengguang
2010-01-06 16:20 ` [PATCH] " Jamie Lokier
2010-01-09 13:44 ` Wu Fengguang
2010-01-06 15:48 ` Christoph Hellwig
2010-01-09 13:52 ` 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=4B443695.5090301@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eparis@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.