[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191212105754.GC1476206@kroah.com>
Date: Thu, 12 Dec 2019 11:57:54 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: syzbot <syzbot+92f32d4e21fb246d31a2@...kaller.appspotmail.com>
Cc: andriy.shevchenko@...ux.intel.com, asierra@...-inc.com,
corbet@....net, ext-kimmo.rautkoski@...sala.com, jslaby@...e.com,
kai.heng.feng@...onical.com, linux-api@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-serial@...r.kernel.org, mika.westerberg@...ux.intel.com,
paulburton@...nel.org, peter@...leysoftware.com, sr@...x.de,
syzkaller-bugs@...glegroups.com, yamada.masahiro@...ionext.com,
yegorslists@...glemail.com
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in
mem16_serial_out
On Mon, Dec 09, 2019 at 05:38:01PM -0800, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit bd94c4077a0b2ecc35562c294f80f3659ecd8499
> Author: Masahiro Yamada <yamada.masahiro@...ionext.com>
> Date: Wed Oct 28 03:46:05 2015 +0000
>
> serial: support 16-bit register interface for console
That would be because that is when this function was added to the kernel
:)
Again, you are asking the kernel to write to a bad place in memory, and
then crash when that happens. That sounds like the correct
functionality to me...
thanks,
greg k-h
Powered by blists - more mailing lists