Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 27 Jul 2022 20:47:41 +0300
From: Alexey Khoroshilov <>
To: Linus Torvalds <>
Cc: Petr Mladek <>, "Paul E. McKenney" <>,
 Alexander Popov <>, Jonathan Corbet <>,
 Andrew Morton <>,
 Thomas Gleixner <>, Peter Zijlstra <>,
 Joerg Roedel <>, Maciej Rozycki <>,
 Muchun Song <>,
 Viresh Kumar <>, Robin Murphy <>,
 Randy Dunlap <>, Lu Baolu <>,
 Kees Cook <>, Luis Chamberlain <>,
 Wei Liu <>, John Ogness <>,
 Andy Shevchenko <>,
 Alexey Kardashevskiy <>,
 Christophe Leroy <>, Jann Horn
 <>, Greg Kroah-Hartman <>,
 Mark Rutland <>, Andy Lutomirski <>,
 Dave Hansen <>,
 Steven Rostedt <>, Thomas Garnier <>,
 Will Deacon <>, Ard Biesheuvel
 <>, Laura Abbott <>,
 David S Miller <>, Borislav Petkov <>,
 Kernel Hardening <>,,
 "open list:DOCUMENTATION" <>,
 Linux Kernel Mailing List <>,,
Subject: Re: [PATCH] Introduce the pkill_on_warn boot parameter

On 27.07.2022 19:42, Linus Torvalds wrote:
> On Wed, Jul 27, 2022 at 9:17 AM Alexey Khoroshilov
> <> wrote:
>> We see a number of cases where WARNING is used to inform userspace that
>> it is doing something wrong, e.g.
> That first case is entirely bogus.
> WARN_ON() should only be used for "This cannot happen, but if it does,
> I want to know how we got here".
> But the second case is fine: Using "pr_warn()" is fine. A kernel
> warning (without a backtrace) is a normal thing for something that is
> deprecated or questionable, and you want to tell the user that "this
> app is doing something wrong".

Agree with the only note that I like the requirement:

* Do not include "BUG"/"WARNING" in format strings manually to make
* these conditions distinguishable from kernel issues.

very much.

Thank you,

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.