From: syzbot <syzbot+3df59a64502c71cab3d5@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,
wangliang74@huawei.com, yuehaibing@huawei.com,
zhangchangzhong@huawei.com
Subject: Re: [syzbot] [net?] WARNING in xfrm6_tunnel_net_exit (4)
Date: Fri, 24 Oct 2025 21:55:02 -0700 [thread overview]
Message-ID: <68fc5826.050a0220.346f24.01f5.GAE@google.com> (raw)
In-Reply-To: <68ec1f21.050a0220.ac43.0010.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=160c5d2f980000
start commit: cf1ea8854e4f Merge tag 'mmc-v6.18-rc1' of git://git.kernel..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=150c5d2f980000
console output: https://syzkaller.appspot.com/x/log.txt?x=110c5d2f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=af9170887d81dea1
dashboard link: https://syzkaller.appspot.com/bug?extid=3df59a64502c71cab3d5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=162c3de2580000
Reported-by: syzbot+3df59a64502c71cab3d5@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-25 4:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-12 21:35 [syzbot] [net?] WARNING in xfrm6_tunnel_net_exit (4) syzbot
2025-10-18 10:48 ` syzbot
2025-10-25 4:55 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-20 11:30 [PATCH net] " Wang Liang
2025-10-20 12:54 ` 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=68fc5826.050a0220.346f24.01f5.GAE@google.com \
--to=syzbot+3df59a64502c71cab3d5@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 \
--cc=wangliang74@huawei.com \
--cc=yuehaibing@huawei.com \
--cc=zhangchangzhong@huawei.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.