From: syzbot <syzbot+999eb23467f83f9bf9bf@syzkaller.appspotmail.com>
To: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
herbert@gondor.apana.org.au, horms@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, sd@queasysnail.net,
steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in xfrm_state_fini (4)
Date: Sun, 19 Oct 2025 18:04:03 -0700 [thread overview]
Message-ID: <68f58a83.a70a0220.205af.001f.GAE@google.com> (raw)
In-Reply-To: <68ec1f21.050a0220.ac43.000f.GAE@google.com>
syzbot has bisected this issue to:
commit b441cf3f8c4b8576639d20c8eb4aa32917602ecd
Author: Sabrina Dubroca <sd@queasysnail.net>
Date: Fri Jul 4 14:54:33 2025 +0000
xfrm: delete x->tunnel as we delete x
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14b49734580000
start commit: 0b4b77eff5f8 doc: fix seg6_flowlabel path
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=16b49734580000
console output: https://syzkaller.appspot.com/x/log.txt?x=12b49734580000
kernel config: https://syzkaller.appspot.com/x/.config?x=61ab7fa743df0ec1
dashboard link: https://syzkaller.appspot.com/bug?extid=999eb23467f83f9bf9bf
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12cc05e2580000
Reported-by: syzbot+999eb23467f83f9bf9bf@syzkaller.appspotmail.com
Fixes: b441cf3f8c4b ("xfrm: delete x->tunnel as we delete x")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-10-20 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-12 21:35 [syzbot] [net?] WARNING in xfrm_state_fini (4) syzbot
2025-10-13 22:45 ` Eric Dumazet
2025-10-13 23:08 ` syzbot
2025-10-20 1:04 ` syzbot [this message]
2025-10-24 22:01 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2025-10-20 11:25 [PATCH net] " Wang Liang
2025-10-20 12:26 ` syzbot
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=68f58a83.a70a0220.205af.001f.GAE@google.com \
--to=syzbot+999eb23467f83f9bf9bf@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=steffen.klassert@secunet.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 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).