[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190909160539.GA989@tigerII.localdomain>
Date: Tue, 10 Sep 2019 01:05:39 +0900
From: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To: 20190819234111.9019-8-keescook@...omium.org
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Christophe Leroy <christophe.leroy@....fr>,
Peter Zijlstra <peterz@...radead.org>,
Drew Davenport <ddavenport@...omium.org>,
Arnd Bergmann <arnd@...db.de>,
"Steven Rostedt (VMware)" <rostedt@...dmis.org>,
Feng Tang <feng.tang@...el.com>,
Petr Mladek <pmladek@...e.com>,
Mauro Carvalho Chehab <mchehab+samsung@...nel.org>,
Borislav Petkov <bp@...e.de>,
YueHaibing <yuehaibing@...wei.com>, linux-arch@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 7/7] bug: Move WARN_ON() "cut here" into exception
handler
On (08/20/19 09:47), Kees Cook wrote:
[..]
> @@ -181,6 +181,15 @@ enum bug_trap_type report_bug(unsigned long bugaddr, struct pt_regs *regs)
> }
> }
>
> + /*
> + * BUG() and WARN_ON() families don't print a custom debug message
> + * before triggering the exception handler, so we must add the
> + * "cut here" line now. WARN() issues its own "cut here" before the
> + * extra debugging message it writes before triggering the handler.
> + */
> + if ((bug->flags & BUGFLAG_NO_CUT_HERE) == 0)
> + printk(KERN_DEFAULT CUT_HERE);
Shouldn't this be pr_warn() or pr_crit()?
-ss
Powered by blists - more mailing lists