From: syzbot <syzbot+9b277e2c2076e2661f61@syzkaller.appspotmail.com>
To: andy@greyhouse.net, davem@davemloft.net, edumazet@google.com,
hdanton@sina.com, j.vosburgh@gmail.com, jhs@mojatatu.com,
jiri@nvidia.com, jiri@resnulli.us, johannes.berg@intel.com,
jv@jvosburgh.net, kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, xiyou.wangcong@gmail.com
Subject: Re: [syzbot] [net?] BUG: sleeping function called from invalid context in synchronize_net
Date: Sat, 20 Jul 2024 14:26:03 -0700 [thread overview]
Message-ID: <0000000000008750c8061db47514@google.com> (raw)
In-Reply-To: <000000000000eb54bf061cfd666a@google.com>
syzbot has bisected this issue to:
commit facd15dfd69122042502d99ab8c9f888b48ee994
Author: Johannes Berg <johannes.berg@intel.com>
Date: Mon Dec 4 20:47:07 2023 +0000
net: core: synchronize link-watch when carrier is queried
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=116d4a1d980000
start commit: 523b23f0bee3 Add linux-next specific files for 20240710
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=136d4a1d980000
console output: https://syzkaller.appspot.com/x/log.txt?x=156d4a1d980000
kernel config: https://syzkaller.appspot.com/x/.config?x=98dd8c4bab5cdce
dashboard link: https://syzkaller.appspot.com/bug?extid=9b277e2c2076e2661f61
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=148611e1980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10ec9585980000
Reported-by: syzbot+9b277e2c2076e2661f61@syzkaller.appspotmail.com
Fixes: facd15dfd691 ("net: core: synchronize link-watch when carrier is queried")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-07-20 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 19:02 [syzbot] [net?] BUG: sleeping function called from invalid context in synchronize_net syzbot
2024-07-11 21:10 ` syzbot
2024-07-11 21:25 ` Jay Vosburgh
2024-07-20 21:26 ` 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=0000000000008750c8061db47514@google.com \
--to=syzbot+9b277e2c2076e2661f61@syzkaller.appspotmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=j.vosburgh@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@nvidia.com \
--cc=jiri@resnulli.us \
--cc=johannes.berg@intel.com \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiyou.wangcong@gmail.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).