[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <88093da62a4b85f015423cbd1ec2f5ad6eb0c5da.camel@HansenPartnership.com>
Date: Tue, 16 Nov 2021 08:07:19 -0500
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Kees Cook <keescook@...omium.org>, Steven Rostedt <rostedt@...dmis.org>
Cc: Lukas Bulwahn <lukas.bulwahn@...il.com>, Alexander Popov
<alex.popov@...ux.com>, Linus Torvalds <torvalds@...ux-foundation.org>,
Jonathan Corbet <corbet@....net>, Paul McKenney <paulmck@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>, Thomas Gleixner
<tglx@...utronix.de>, Peter Zijlstra <peterz@...radead.org>, Joerg Roedel
<jroedel@...e.de>, Maciej Rozycki <macro@...am.me.uk>, Muchun Song
<songmuchun@...edance.com>, Viresh Kumar <viresh.kumar@...aro.org>, Robin
Murphy <robin.murphy@....com>, Randy Dunlap <rdunlap@...radead.org>, Lu
Baolu <baolu.lu@...ux.intel.com>, Petr Mladek <pmladek@...e.com>, Luis
Chamberlain <mcgrof@...nel.org>, Wei Liu <wl@....org>, John Ogness
<john.ogness@...utronix.de>, Andy Shevchenko
<andriy.shevchenko@...ux.intel.com>, Alexey Kardashevskiy <aik@...abs.ru>,
Christophe Leroy <christophe.leroy@...roup.eu>, Jann Horn
<jannh@...gle.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Mark
Rutland <mark.rutland@....com>, Andy Lutomirski <luto@...nel.org>, Dave
Hansen <dave.hansen@...ux.intel.com>, Will Deacon <will@...nel.org>, Ard
Biesheuvel <ardb@...nel.org>, Laura Abbott <labbott@...nel.org>, David S
Miller <davem@...emloft.net>, Borislav Petkov <bp@...en8.de>, Arnd Bergmann
<arnd@...db.de>, Andrew Scull <ascull@...gle.com>, Marc Zyngier
<maz@...nel.org>, Jessica Yu <jeyu@...nel.org>, Iurii Zaikin
<yzaikin@...gle.com>, Rasmus Villemoes <linux@...musvillemoes.dk>, Wang
Qing <wangqing@...o.com>, Mel Gorman <mgorman@...e.de>, Mauro Carvalho
Chehab <mchehab+huawei@...nel.org>, Andrew Klychkov
<andrew.a.klychkov@...il.com>, Mathieu Chouquet-Stringer
<me@...hieu.digital>, Daniel Borkmann <daniel@...earbox.net>, Stephen Kitt
<steve@....org>, Stephen Boyd <sboyd@...nel.org>, Thomas Bogendoerfer
<tsbogend@...ha.franken.de>, Mike Rapoport <rppt@...nel.org>, Bjorn
Andersson <bjorn.andersson@...aro.org>, Kernel Hardening
<kernel-hardening@...ts.openwall.com>, linux-hardening@...r.kernel.org,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>, linux-arch
<linux-arch@...r.kernel.org>, Linux Kernel Mailing List
<linux-kernel@...r.kernel.org>, linux-fsdevel
<linux-fsdevel@...r.kernel.org>, notify@...nel.org, main@...ts.elisa.tech,
safety-architecture@...ts.elisa.tech, devel@...ts.elisa.tech, Shuah Khan
<shuah@...nel.org>
Subject: Re: [PATCH v2 0/2] Introduce the pkill_on_warn parameter
On Mon, 2021-11-15 at 14:06 -0800, Kees Cook wrote:
> On Mon, Nov 15, 2021 at 11:06:49AM -0500, Steven Rostedt wrote:
> > On Mon, 15 Nov 2021 14:59:57 +0100
> > Lukas Bulwahn <lukas.bulwahn@...il.com> wrote:
> >
> > > 1. Allow a reasonably configured kernel to boot and run with
> > > panic_on_warn set. Warnings should only be raised when something
> > > is not configured as the developers expect it or the kernel is
> > > put into a state that generally is _unexpected_ and has been
> > > exposed little to the critical thought of the developer, to
> > > testing efforts and use in other systems in the wild. Warnings
> > > should not be used for something informative, which still allows
> > > the kernel to continue running in a proper way in a generally
> > > expected environment. Up to my knowledge, there are some kernels
> > > in production that run with panic_on_warn; so, IMHO, this
> > > requirement is generally accepted (we might of course
> >
> > To me, WARN*() is the same as BUG*(). If it gets hit, it's a bug in
> > the kernel and needs to be fixed. I have several WARN*() calls in
> > my code, and it's all because the algorithms used is expected to
> > prevent the condition in the warning from happening. If the warning
> > triggers, it means either that the algorithm is wrong or my
> > assumption about the algorithm is wrong. In either case, the kernel
> > needs to be updated. All my tests fail if a WARN*() gets hit
> > (anywhere in the kernel, not just my own).
> >
> > After reading all the replies and thinking about this more, I find
> > the pkill_on_warning actually worse than not doing anything. If you
> > are concerned about exploits from warnings, the only real solution
> > is a panic_on_warning. Yes, it brings down the system, but really,
> > it has to be brought down anyway, because it is in need of a kernel
> > update.
>
> Hmm, yes. What it originally boiled down to, which is why Linus first
> objected to BUG(), was that we don't know what other parts of the
> system have been disrupted. The best example is just that of locking:
> if we BUG() or do_exit() in the middle of holding a lock, we'll wreck
> whatever subsystem that was attached to. Without a deterministic
> system state unwinder, there really isn't a "safe" way to just stop a
> kernel thread.
But this misses the real point: the majority of WARN conditions are in
device drivers checking expected device state against an internal state
model. If this triggers it's a problem with the device not the thread,
so killing the thread is blaming the wrong party and making the
situation worse because it didn't do anything to address the actual
problem.
> With this pkill_on_warn, we avoid the BUG problem (since the thread
> of execution continues and stops at an 'expected' place: the signal
> handler).
And what about the unexpected state?
> However, now we have the newer objection from Linus, which is one of
> attribution: the WARN might be hit during an "unrelated" thread of
> execution and "current" gets blamed, etc. And beyond that, if we take
> down a portion of userspace, what in userspace may be destabilized?
> In theory, we get a case where any required daemons would be
> restarted by init, but that's not "known".
>
> The safest version of this I can think of is for processes to opt
> into this mitigation. That would also cover the "special cases" we've
> seen exposed too. i.e. init and kthreads would not opt in.
>
> However, that's a lot to implement when Marco's tracing suggestion
> might be sufficient and policy could be entirely implemented in
> userspace. It could be as simple as this (totally untested):
Really, no, this is precisely wrong thinking. If the condition were
recoverable it wouldn't result in a WARN. There are some WARNs where
we think the condition is unexpected enough not to bother adding error
handling (we need these reporting so we know that the assumption was
wrong), but for most if there were a way to handle it we'd have built
it into the usual error flow. What WARN means is that an unexpected
condition occurred which means the kernel itself is in an unknown
state. You can't recover from that by killing and restarting random
stuff, you have to reinitialize to a known state (i.e. reset the
system). Some of the reason we do WARN instead of BUG is that we
believe the state contamination is limited and if you're careful the
system can continue in a degraded state if the user wants to accept the
risk. Thinking the user can handle the state reset locally by some
preset policy is pure fantasy: if we didn't know how to fix it at the
point it occurred, why would something far away from the action when
most of the information has been lost have a better chance?
Your only policy choices when hitting WARN are
1. Accept the risk and continue degraded operation, or
2. reset the system to a known good state.
James
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
