[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <74859736-478a-6ad7-f0be-cfe87ec40ff5@i-love.sakura.ne.jp>
Date: Fri, 13 Dec 2019 23:31:08 +0900
From: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To: Dmitry Vyukov <dvyukov@...gle.com>,
Greg KH <gregkh@...uxfoundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Cc: syzbot <syzbot+f4f1e871965064ae689e@...kaller.appspotmail.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
asierra@...-inc.com, ext-kimmo.rautkoski@...sala.com,
Jiri Slaby <jslaby@...e.com>,
kai heng feng <kai.heng.feng@...onical.com>,
LKML <linux-kernel@...r.kernel.org>,
linux-serial <linux-serial@...r.kernel.org>,
mika.westerberg@...ux.intel.com, o.barta89@...il.com,
paulburton@...nel.org, sr@...x.de,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
yegorslists@...glemail.com
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in
mem_serial_out
On 2019/12/13 19:00, Dmitry Vyukov wrote:
> Easier said than done. "normal user of the serial port" is not really
> a thing in Linux, right? You either have CAP_SYS_ADMIN or not, that's
> not per-device...
> As far as I remember +Tetsuo proposed a config along the lines of
> "restrict only things that legitimately cause damage under a fuzzer
> workload", e.g. freezing filesystems, disabling console output, etc.
> This may be another candidate. But I can't find where that proposal is
> now.
That suggestion got no response for two months.
https://lkml.kernel.org/r/3e4e2b6b-7828-54ab-cf28-db1a396d7e20@i-love.sakura.ne.jp
Unless we add such kernel config option to upstream kernels, it will become
a whack-a-mole game.
Powered by blists - more mailing lists