From: syzbot <syzbot+b471b7c936301a59745b@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, hdanton@sina.com,
jchapman@katalix.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, samuel.thibault@ens-lyon.org,
syzkaller-bugs@googlegroups.com, tparkin@katalix.com
Subject: Re: [syzbot] [net?] KASAN: slab-use-after-free Read in l2tp_tunnel_del_work
Date: Tue, 02 Jul 2024 15:51:02 -0700 [thread overview]
Message-ID: <0000000000004a4df5061c4b8cf3@google.com> (raw)
In-Reply-To: <000000000000454110061bb48619@google.com>
syzbot has bisected this issue to:
commit d18d3f0a24fc4a3513495892ab1a3753628b341b
Author: James Chapman <jchapman@katalix.com>
Date: Thu Jun 20 11:22:44 2024 +0000
l2tp: replace hlist with simple list for per-tunnel session list
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=110dc9c6980000
start commit: 1c5fc27bc48a Merge tag 'nf-next-24-06-28' of git://git.ker..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=130dc9c6980000
console output: https://syzkaller.appspot.com/x/log.txt?x=150dc9c6980000
kernel config: https://syzkaller.appspot.com/x/.config?x=5264b58fdff6e881
dashboard link: https://syzkaller.appspot.com/bug?extid=b471b7c936301a59745b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1094f701980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16bf2361980000
Reported-by: syzbot+b471b7c936301a59745b@syzkaller.appspotmail.com
Fixes: d18d3f0a24fc ("l2tp: replace hlist with simple list for per-tunnel session list")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-07-02 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 10:40 [syzbot] [net?] KASAN: slab-use-after-free Read in l2tp_tunnel_del_work syzbot
2024-06-28 10:28 ` Hillf Danton
2024-06-28 12:20 ` syzbot
2024-07-01 16:12 ` syzbot
2024-07-01 16:51 ` James Chapman
2024-07-02 22:51 ` 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=0000000000004a4df5061c4b8cf3@google.com \
--to=syzbot+b471b7c936301a59745b@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=jchapman@katalix.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=samuel.thibault@ens-lyon.org \
--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 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.