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
| ||
|
Date: Tue, 24 Mar 2020 17:42:52 +0100 From: Greg KH <gregkh@...uxfoundation.org> To: Will Deacon <will@...nel.org> Cc: linux-kernel@...r.kernel.org, Eric Dumazet <edumazet@...gle.com>, Jann Horn <jannh@...gle.com>, Kees Cook <keescook@...omium.org>, Maddie Stone <maddiestone@...gle.com>, Marco Elver <elver@...gle.com>, "Paul E . McKenney" <paulmck@...nel.org>, Peter Zijlstra <peterz@...radead.org>, Thomas Gleixner <tglx@...utronix.de>, kernel-team@...roid.com, kernel-hardening@...ts.openwall.com Subject: Re: [RFC PATCH 14/21] plist: Use CHECK_DATA_CORRUPTION instead of explicit {BUG,WARN}_ON() On Tue, Mar 24, 2020 at 03:36:36PM +0000, Will Deacon wrote: > CHECK_DATA_CORRUPTION() allows detected data corruption to result > consistently in either a BUG() or a WARN() depending on > CONFIG_BUG_ON_DATA_CORRUPTION. > > Use CHECK_DATA_CORRUPTION() to report plist integrity checking failures, > rather than explicit use of BUG_ON() and WARN_ON(). > > Cc: Kees Cook <keescook@...omium.org> > Cc: Paul E. McKenney <paulmck@...nel.org> > Cc: Peter Zijlstra <peterz@...radead.org> > Signed-off-by: Will Deacon <will@...nel.org> Reviewed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Powered by blists - more mailing lists