| 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: Thu, 17 Nov 2022 15:28:44 -0800
From: Kees Cook <keescook@...omium.org>
To: Marco Elver <elver@...gle.com>
Cc: Jann Horn <jannh@...gle.com>, Dmitry Vyukov <dvyukov@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
Juri Lelli <juri.lelli@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Valentin Schneider <vschneid@...hat.com>,
Andrey Ryabinin <ryabinin.a.a@...il.com>,
Alexander Potapenko <glider@...gle.com>,
Andrey Konovalov <andreyknvl@...il.com>,
Vincenzo Frascino <vincenzo.frascino@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
Luis Chamberlain <mcgrof@...nel.org>,
David Gow <davidgow@...gle.com>,
tangmeng <tangmeng@...ontech.com>,
Petr Mladek <pmladek@...e.com>,
"Paul E. McKenney" <paulmck@...nel.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
"Guilherme G. Piccoli" <gpiccoli@...lia.com>,
Tiezhu Yang <yangtiezhu@...ngson.cn>,
kasan-dev@...glegroups.com, linux-mm@...ck.org,
Greg KH <gregkh@...uxfoundation.org>,
Linus Torvalds <torvalds@...uxfoundation.org>,
Seth Jenkins <sethjenkins@...gle.com>,
Andy Lutomirski <luto@...nel.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Arnd Bergmann <arnd@...db.de>,
Jonathan Corbet <corbet@....net>,
Baolin Wang <baolin.wang@...ux.alibaba.com>,
"Jason A. Donenfeld" <Jason@...c4.com>,
Eric Biggers <ebiggers@...gle.com>,
Huang Ying <ying.huang@...el.com>,
Anton Vorontsov <anton@...msg.org>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
Laurent Dufour <ldufour@...ux.ibm.com>,
Rob Herring <robh@...nel.org>, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH v2 4/6] panic: Consolidate open-coded panic_on_warn checks
On Mon, Nov 14, 2022 at 10:57:15AM +0100, Marco Elver wrote:
> On Wed, 9 Nov 2022 at 21:00, Kees Cook <keescook@...omium.org> wrote:
> >
> > Several run-time checkers (KASAN, UBSAN, KFENCE, KCSAN, sched) roll
> > their own warnings, and each check "panic_on_warn". Consolidate this
> > into a single function so that future instrumentation can be added in
> > a single location.
> >
> > Cc: Marco Elver <elver@...gle.com>
> > Cc: Dmitry Vyukov <dvyukov@...gle.com>
> > Cc: Peter Zijlstra <peterz@...radead.org>
> > Cc: Juri Lelli <juri.lelli@...hat.com>
> > Cc: Vincent Guittot <vincent.guittot@...aro.org>
> > Cc: Dietmar Eggemann <dietmar.eggemann@....com>
> > Cc: Steven Rostedt <rostedt@...dmis.org>
> > Cc: Ben Segall <bsegall@...gle.com>
> > Cc: Mel Gorman <mgorman@...e.de>
> > Cc: Daniel Bristot de Oliveira <bristot@...hat.com>
> > Cc: Valentin Schneider <vschneid@...hat.com>
> > Cc: Andrey Ryabinin <ryabinin.a.a@...il.com>
> > Cc: Alexander Potapenko <glider@...gle.com>
> > Cc: Andrey Konovalov <andreyknvl@...il.com>
> > Cc: Vincenzo Frascino <vincenzo.frascino@....com>
> > Cc: Andrew Morton <akpm@...ux-foundation.org>
> > Cc: Luis Chamberlain <mcgrof@...nel.org>
> > Cc: David Gow <davidgow@...gle.com>
> > Cc: tangmeng <tangmeng@...ontech.com>
> > Cc: Jann Horn <jannh@...gle.com>
> > Cc: Petr Mladek <pmladek@...e.com>
> > Cc: "Paul E. McKenney" <paulmck@...nel.org>
> > Cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
> > Cc: "Guilherme G. Piccoli" <gpiccoli@...lia.com>
> > Cc: Tiezhu Yang <yangtiezhu@...ngson.cn>
> > Cc: kasan-dev@...glegroups.com
> > Cc: linux-mm@...ck.org
> > Signed-off-by: Kees Cook <keescook@...omium.org>
> > ---
> > include/linux/panic.h | 1 +
> > kernel/kcsan/report.c | 3 +--
> > kernel/panic.c | 9 +++++++--
> > kernel/sched/core.c | 3 +--
> > lib/ubsan.c | 3 +--
> > mm/kasan/report.c | 4 ++--
> > mm/kfence/report.c | 3 +--
> > 7 files changed, 14 insertions(+), 12 deletions(-)
> >
> > diff --git a/include/linux/panic.h b/include/linux/panic.h
> > index c7759b3f2045..1702aeb74927 100644
> > --- a/include/linux/panic.h
> > +++ b/include/linux/panic.h
> > @@ -11,6 +11,7 @@ extern long (*panic_blink)(int state);
> > __printf(1, 2)
> > void panic(const char *fmt, ...) __noreturn __cold;
> > void nmi_panic(struct pt_regs *regs, const char *msg);
> > +void check_panic_on_warn(const char *reason);
> > extern void oops_enter(void);
> > extern void oops_exit(void);
> > extern bool oops_may_print(void);
> > diff --git a/kernel/kcsan/report.c b/kernel/kcsan/report.c
> > index 67794404042a..e95ce7d7a76e 100644
> > --- a/kernel/kcsan/report.c
> > +++ b/kernel/kcsan/report.c
> > @@ -492,8 +492,7 @@ static void print_report(enum kcsan_value_change value_change,
> > dump_stack_print_info(KERN_DEFAULT);
> > pr_err("==================================================================\n");
> >
> > - if (panic_on_warn)
> > - panic("panic_on_warn set ...\n");
> > + check_panic_on_warn("KCSAN");
> > }
> >
> > static void release_report(unsigned long *flags, struct other_info *other_info)
> > diff --git a/kernel/panic.c b/kernel/panic.c
> > index 129936511380..3afd234767bc 100644
> > --- a/kernel/panic.c
> > +++ b/kernel/panic.c
> > @@ -201,6 +201,12 @@ static void panic_print_sys_info(bool console_flush)
> > ftrace_dump(DUMP_ALL);
> > }
> >
> > +void check_panic_on_warn(const char *reason)
> > +{
> > + if (panic_on_warn)
> > + panic("%s: panic_on_warn set ...\n", reason);
> > +}
> > +
> > /**
> > * panic - halt the system
> > * @fmt: The text string to print
> > @@ -619,8 +625,7 @@ void __warn(const char *file, int line, void *caller, unsigned taint,
> > if (regs)
> > show_regs(regs);
> >
> > - if (panic_on_warn)
> > - panic("panic_on_warn set ...\n");
> > + check_panic_on_warn("kernel");
>
> What is the reason "kernel" in this context? The real reason is a WARN
> - so would the reason "WARNING" be more intuitive?
I'll rename "reason" to "origin" or something -- it's mainly to see
who was calling this when it's not core kernel logic.
--
Kees Cook
Powered by blists - more mailing lists