From: syzbot <syzbot+99efc1c133eff186721a@syzkaller.appspotmail.com>
To: andrew@lunn.ch, davem@davemloft.net, hkallweit1@gmail.com,
jakub.kicinski@netronome.com, johan.hedberg@gmail.com,
kuba@kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, marcel@holtmann.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: INFO: trying to register non-static key in skb_queue_purge
Date: Fri, 31 Jul 2020 17:17:06 -0700 [thread overview]
Message-ID: <0000000000005b507905abc5d32f@google.com> (raw)
In-Reply-To: <000000000000f796a105abbfa33d@google.com>
syzbot has bisected this issue to:
commit 65b27995a4ab8fc51b4adc6b4dcdca20f7a595bb
Author: Heiner Kallweit <hkallweit1@gmail.com>
Date: Mon Aug 12 21:52:19 2019 +0000
net: phy: let phy_speed_down/up support speeds >1Gbps
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1327ef50900000
start commit: 83bdc727 random32: remove net_rand_state from the latent e..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=10a7ef50900000
console output: https://syzkaller.appspot.com/x/log.txt?x=1727ef50900000
kernel config: https://syzkaller.appspot.com/x/.config?x=e59ee776d5aa8d55
dashboard link: https://syzkaller.appspot.com/bug?extid=99efc1c133eff186721a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12429014900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12dbc404900000
Reported-by: syzbot+99efc1c133eff186721a@syzkaller.appspotmail.com
Fixes: 65b27995a4ab ("net: phy: let phy_speed_down/up support speeds >1Gbps")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-08-01 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 16:54 INFO: trying to register non-static key in skb_queue_purge syzbot
2020-08-01 0:17 ` syzbot [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=0000000000005b507905abc5d32f@google.com \
--to=syzbot+99efc1c133eff186721a@syzkaller.appspotmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--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.