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  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]
Date:   Thu, 7 May 2020 16:42:19 -0400
From:   Rafael Aquini <>
To:     Qian Cai <>
Cc:     Andrew Morton <>,
        LKML <>,,,,, Baoquan He <>,
        Jonathan Corbet <>,
        Luis Chamberlain <>,
        Kees Cook <>
Subject: Re: [PATCH] kernel: add panic_on_taint

On Wed, May 06, 2020 at 10:50:19PM -0400, Qian Cai wrote:
> > On May 6, 2020, at 6:28 PM, Rafael Aquini <> wrote:
> > 
> > Analogously to the introduction of panic_on_warn, this patch
> > introduces a kernel option named panic_on_taint in order to
> > provide a simple and generic way to stop execution and catch
> > a coredump when the kernel gets tainted by any given taint flag.
> > 
> > This is useful for debugging sessions as it avoids rebuilding
> > the kernel to explicitly add calls to panic() or BUG() into
> > code sites that introduce the taint flags of interest.
> > Another, perhaps less frequent, use for this option would be
> > as a mean for assuring a security policy (in paranoid mode)
> > case where no single taint is allowed for the running system.
> Andrew, you can drop the patch below from -mm now because that one is now obsolete,
> mm-slub-add-panic_on_error-to-the-debug-facilities.patch
Please, don't drop it yet. I'll send a patch to get rid of the bits,
once this one gets accepted, if it gets accepted.

-- Rafael 

Powered by blists - more mailing lists