linux-kernel - Re: [PATCH] log2.h: Macro-ize is_power_of_2() for use in BUILD_BUG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100106134232.0025e818.akpm@linux-foundation.org>
Date:	Wed, 6 Jan 2010 13:42:32 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Roland Dreier <rdreier@...co.com>
Cc:	linux-kernel@...r.kernel.org,
	Bart Van Assche <bart.vanassche@...il.com>,
	David Dillow <dave@...dillows.org>
Subject: Re: [PATCH] log2.h: Macro-ize is_power_of_2() for use in
 BUILD_BUG_ON

On Wed, 06 Jan 2010 12:44:05 -0800
Roland Dreier <rdreier@...co.com> wrote:

> 
>  > Perhaps we can avoid worrying about that via
> 
>  > #define BUILD_BUG_ON_NOT_POWER_OF_2(n)	\
>  > 	BUILD_BUG_ON((n != 0 && ((n & (n - 1)) == 0)))
> 
> Having something so specific to this particular case makes me feel like
> maybe it's just not worth it.

mm..  I think _something_ is worth it.  The requirement that a constant
be a power of two is a very common one in the kernel.

If you feel strongly about it and think the incremental benefit of your
version is worth the effort of screening out gcc warts then ho hum, go
for it I guess.

>  At least in the case I'm looking at, we
> could just have:
> 
> /*
>  * The code relies on FOO being a power of 2.  If you break this,
>  * you're dumb.
>  */
> #define FOO_SHIFT	6
> #define FOO		(1 << FOO_SHIFT)
> 
> Your thoughts?

Given the probably-hundreds of sites which could utilise this assertion,
that approach will be a bit of a PITA.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/