From: syzbot <syzbot+20b90969babe05609947@syzkaller.appspotmail.com>
To: andrew@lunn.ch, davem@davemloft.net, dledford@redhat.com,
f.fainelli@gmail.com, hkallweit1@gmail.com, jgg@ziepe.ca,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, linux@armlinux.org.uk,
netdev@vger.kernel.org, rkovhaev@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in netdevice_event_work_handler
Date: Wed, 22 Jul 2020 13:29:04 -0700 [thread overview]
Message-ID: <00000000000041388e05ab0d97aa@google.com> (raw)
In-Reply-To: <0000000000005b9fca05aa0af1b9@google.com>
syzbot has bisected this issue to:
commit d70c47c8dc6902db19555b7ff7e6eeb264d4ac06
Author: Heiner Kallweit <hkallweit1@gmail.com>
Date: Thu Apr 23 19:34:33 2020 +0000
net: phy: make phy_suspend a no-op if PHY is suspended already
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16b2aad8900000
start commit: 0bddd227 Documentation: update for gcc 4.9 requirement
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=15b2aad8900000
console output: https://syzkaller.appspot.com/x/log.txt?x=11b2aad8900000
kernel config: https://syzkaller.appspot.com/x/.config?x=66ad203c2bb6d8b
dashboard link: https://syzkaller.appspot.com/bug?extid=20b90969babe05609947
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12a8edff100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167d3bb7100000
Reported-by: syzbot+20b90969babe05609947@syzkaller.appspotmail.com
Fixes: d70c47c8dc69 ("net: phy: make phy_suspend a no-op if PHY is suspended already")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-07-22 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 23:54 KASAN: use-after-free Read in netdevice_event_work_handler syzbot
2020-07-22 20:29 ` syzbot [this message]
2020-07-31 21:11 ` Rustam Kovhaev
2020-08-01 2:23 ` Rustam Kovhaev
2020-08-02 22:22 ` Jason Gunthorpe
2020-08-04 20:00 ` Rustam Kovhaev
2020-08-05 15:20 ` Jason Gunthorpe
[not found] <20200731211122.GA1728751 () thinkpad>
2020-08-01 2:06 ` Coiby Xu
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=00000000000041388e05ab0d97aa@google.com \
--to=syzbot+20b90969babe05609947@syzkaller.appspotmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=rkovhaev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.