From: Greg KH <greg@kroah.com>
To: syzbot <syzbot+a7ebdb01bb2cc165cab6@syzkaller.appspotmail.com>
Cc: Markus.Elfring@web.de, UNGLinuxDriver@microchip.com,
davem@davemloft.net, dingxiang@cmss.chinamobile.com,
hdanton@sina.com, kuba@kernel.org, linus.walleij@linaro.org,
linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, steve.glendinning@shawell.net,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in __smsc95xx_mdio_read
Date: Sun, 26 Jul 2020 12:03:28 +0200 [thread overview]
Message-ID: <20200726100328.GA1273266@kroah.com> (raw)
In-Reply-To: <00000000000083581705ab553aab@google.com>
On Sun, Jul 26, 2020 at 02:57:05AM -0700, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 7e23ab72e73bc601b4cf2983382691d9f165c8d1
> Author: Ding Xiang <dingxiang@cmss.chinamobile.com>
> Date: Mon Mar 30 07:56:26 2020 +0000
>
> pinctrl: nomadik:remove unneeded variable
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13cfe3a0900000
> start commit: 7ae77150 Merge tag 'powerpc-5.8-1' of git://git.kernel.org..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=d195fe572fb15312
> dashboard link: https://syzkaller.appspot.com/bug?extid=a7ebdb01bb2cc165cab6
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17046c66100000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=140a8a3e100000
>
> If the result looks correct, please mark the issue as fixed by replying with:
I think the bisection logic needs to be worked on a bit better, as how
can this patch resolve the reported problem?
thanks,
greg k-h
prev parent reply other threads:[~2020-07-26 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000a376c105a8313901@google.com>
2020-07-26 9:57 ` KASAN: use-after-free Read in __smsc95xx_mdio_read syzbot
2020-07-26 10:03 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200726100328.GA1273266@kroah.com \
--to=greg@kroah.com \
--cc=Markus.Elfring@web.de \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=dingxiang@cmss.chinamobile.com \
--cc=hdanton@sina.com \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steve.glendinning@shawell.net \
--cc=syzbot+a7ebdb01bb2cc165cab6@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).