From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roland Dreier Subject: Re: [PATCH] fs: O_* bit numbers uniqueness check Date: Tue, 05 Jan 2010 23:08:08 -0800 Message-ID: References: <20100106065526.GB11368@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andrew Morton , David Miller , Stephen Rothwell , Al Viro , Christoph Hellwig , Eric Paris , LKML , linux-fsdevel@vger.kernel.org To: Wu Fengguang Return-path: Received: from sj-iport-4.cisco.com ([171.68.10.86]:53140 "EHLO sj-iport-4.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751656Ab0AFHIP (ORCPT ); Wed, 6 Jan 2010 02:08:15 -0500 In-Reply-To: <20100106065526.GB11368@localhost> (Wu Fengguang's message of "Wed, 6 Jan 2010 14:55:26 +0800") Sender: linux-fsdevel-owner@vger.kernel.org List-ID: > + /* please add new bits here to ensure allocation uniqueness */ > + BUG_ON(20 != hweight32( > + O_RDONLY | O_WRONLY | O_RDWR | I wonder if there's a way to make this BUILD_BUG_ON(), so the problem is caught at compile time (a change like adding an O_ flag is often compile tested only for obscure archs). One could create a compile-time macro-ized version of hweight32() and use that, I guess, although I'm not sure it's worth the ugliness. Failing that maybe this should be WARN_ON()? I'd be annoyed if my arch wouldn't boot because some strange new O_ flag happened to collide. - R.