From: syzbot <syzbot+332fe1e67018625f63c9@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, guohui.study@gmail.com,
horms@kernel.org, jchapman@katalix.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com,
tparkin@katalix.com
Subject: Re: [syzbot] [net?] WARNING in l2tp_exit_net
Date: Fri, 15 Nov 2024 15:03:03 -0800 [thread overview]
Message-ID: <6737d327.050a0220.57553.0040.GAE@google.com> (raw)
In-Reply-To: <0000000000005423e30621f745ff@google.com>
syzbot has bisected this issue to:
commit 73d33bd063c4cfef3db17f9bec3d202928ed8631
Author: James Chapman <jchapman@katalix.com>
Date: Fri Aug 23 14:22:57 2024 +0000
l2tp: avoid using drain_workqueue in l2tp_pre_exit_net
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1306eb5f980000
start commit: ccb35037c48a Merge branch 'net-lan969x-add-vcap-functional..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1086eb5f980000
console output: https://syzkaller.appspot.com/x/log.txt?x=1706eb5f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=a9d1c42858837b59
dashboard link: https://syzkaller.appspot.com/bug?extid=332fe1e67018625f63c9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=136a36a7980000
Reported-by: syzbot+332fe1e67018625f63c9@syzkaller.appspotmail.com
Fixes: 73d33bd063c4 ("l2tp: avoid using drain_workqueue in l2tp_pre_exit_net")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-11-15 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 2:49 [syzbot] [net?] WARNING in l2tp_exit_net syzbot
2024-09-13 13:39 ` James Chapman
2024-11-06 6:00 ` syzbot
2024-11-15 23:03 ` 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=6737d327.050a0220.57553.0040.GAE@google.com \
--to=syzbot+332fe1e67018625f63c9@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guohui.study@gmail.com \
--cc=horms@kernel.org \
--cc=jchapman@katalix.com \
--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=tparkin@katalix.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).