From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wu Fengguang Subject: Re: [PATCH] fs: O_* bit numbers uniqueness check Date: Wed, 6 Jan 2010 15:20:29 +0800 Message-ID: <20100106072029.GA25169@localhost> References: <20100106065526.GB11368@localhost> <4B443695.5090301@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Andrew Morton , David Miller , Stephen Rothwell , Al Viro , Christoph Hellwig , Eric Paris , LKML , "linux-fsdevel@vger.kernel.org" To: Eric Dumazet Return-path: Content-Disposition: inline In-Reply-To: <4B443695.5090301@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, Jan 06, 2010 at 03:07:01PM +0800, Eric Dumazet wrote: > Le 06/01/2010 07:55, Wu Fengguang a =C3=A9crit : > > The O_* bit numbers are defined in 20+ arch/*, and hence can silent= ly > > overlap. Add a boot time check to ensure the uniqueness as suggeste= d > > by David Miller. > >=20 > > CC: David Miller > > CC: Stephen Rothwell > > CC: Al Viro > > CC: Christoph Hellwig > > CC: Eric Paris > > Signed-off-by: Wu Fengguang > > --- > > { > > + /* please add new bits here to ensure allocation uniqueness */ > > + BUG_ON(20 !=3D 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)); > > + >=20 > I cannot test it, but given O_RDONLY is 0, are you sure 20 bits are a= ctually set ? Yes, I tested it. The tricky one is O_SYNC, which actually has two bits= =2E. Thanks, =46engguang