linux-kernel - [PATCH 0/2] Stop some of the abuse of BUG() where compile time checks should be used.

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 21 Nov 2011 17:31:04 -0800
From:	David Daney <ddaney.cavm@...il.com>
To:	ralf@...ux-mips.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	David Rientjes <rientjes@...gle.com>
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	David Daney <david.daney@...ium.com>
Subject: [PATCH 0/2] Stop some of the abuse of BUG() where compile time checks should be used.

From: David Daney <david.daney@...ium.com>

After some, perhaps justified, reluctance to merge dummy symbol
definitions  containing BUG() into header files, I propose these patches
instead.

We define a new compile time assertion BUILD_BUG_ON_USED() that can be
used in places were we expect the compiler's dead code elimination to
get rid of code.  This happens mostly in code dealing with huge pages,
but in other places as well.

The first patch adds BUILD_BUG_ON_USED(), the second gets rid of one
of the main abusers of BUG().

David Daney (2):
  kernel.h: Add BUILD_BUG_ON_USED() macro.
  hugetlb: Replace BUG() with BUILD_BUG_ON_USED() for dummy
    definitions.

 include/linux/compiler-gcc4.h |    1 +
 include/linux/compiler.h      |    4 +++-
 include/linux/hugetlb.h       |   15 ++++++++-------
 include/linux/kernel.h        |   16 ++++++++++++++++
 4 files changed, 28 insertions(+), 8 deletions(-)

-- 
1.7.2.3

--
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/