[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200131133726.GE10381@localhost>
Date: Fri, 31 Jan 2020 14:37:26 +0100
From: Johan Hovold <johan@...nel.org>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: Dan Carpenter <dan.carpenter@...cle.com>,
syzkaller <syzkaller@...glegroups.com>,
Eric Dumazet <edumazet@...gle.com>,
Steven Rostedt <rostedt@...dmis.org>,
Hillf Danton <hdanton@...a.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alan Stern <stern@...land.harvard.edu>,
syzbot <syzbot+1bc2c2afd44f820a669f@...kaller.appspotmail.com>,
Andrey Konovalov <andreyknvl@...gle.com>,
ingrassia@...genesys.com, LKML <linux-kernel@...r.kernel.org>,
USB list <linux-usb@...r.kernel.org>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: [PATCH] usb: core: urb: change a dev_WARN() to dev_err() for
syzbot
On Fri, Jan 31, 2020 at 12:19:39PM +0100, Dmitry Vyukov wrote:
> I see lots of people also mention panic_on_warn in the context of
> these reports. panic_on_warn here is only a red herring. It really
> does not change anything. We could remove it, but still report
> WARNINGs. But syzkaller also reports some things that don't panic
> anyway. This is really about the criteria for kernel bug vs non-bug
> (something that needs to be reported or not).
Mentioning panic_on_warn is relevant to determine whether a fix needs to
be backported or not. Some of the bugs in question are mostly benign in
the sense that they are unlikely to crash your machine, but we'd still
want them in in stable due to panic_on_warn and automatic testing.
Johan
Powered by blists - more mailing lists