linux-kernel - Re: [PATCH] debug: Deprecate BUG_ON() use in new code, introduce CRASH

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFLxGvzrSUfEV+LM26yy6aeA7hqGt0PnuuBD6rWDhRnivSRSmQ@mail.gmail.com>
Date:	Mon, 8 Jun 2015 10:08:17 +0200
From:	Richard Weinberger <richard.weinberger@...il.com>
To:	Alexander Holler <holler@...oftware.de>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Tejun Heo <htejun@...il.com>,
	Louis Langholtz <lou_langholtz@...com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Trivial patch monkey <trivial@...nel.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] debug: Deprecate BUG_ON() use in new code, introduce CRASH_ON()

On Mon, Jun 8, 2015 at 9:40 AM, Alexander Holler <holler@...oftware.de> wrote:
> Am 08.06.2015 um 09:12 schrieb Ingo Molnar:
>>
>>
>> * Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>>
>>> Stop with the random BUG_ON() additions.
>>
>>
>> Yeah, so I propose the attached patch which attempts to resist new
>> BUG_ON()
>> additions.
>
>
> As this reminded me at flame I received once from a maintainer because I
> wanted to avoid a desastrous memory corruption by using a BUG_ON().

Reference?

-- 
Thanks,
//richard
--
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/