From: syzbot <syzbot+3df59a64502c71cab3d5@syzkaller.appspotmail.com>
To: davem@davemloft.net, 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, 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: Mon, 20 Oct 2025 05:54:02 -0700 [thread overview]
Message-ID: <68f630ea.050a0220.91a22.0448.GAE@google.com> (raw)
In-Reply-To: <20251020113026.2461281-1-wangliang74@huawei.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+3df59a64502c71cab3d5@syzkaller.appspotmail.com
Tested-by: syzbot+3df59a64502c71cab3d5@syzkaller.appspotmail.com
Tested on:
commit: 211ddde0 Linux 6.18-rc2
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1564dde2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=af9170887d81dea1
dashboard link: https://syzkaller.appspot.com/bug?extid=3df59a64502c71cab3d5
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=1450dde2580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-10-20 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 11:30 [PATCH net] Re: [syzbot] [net?] WARNING in xfrm6_tunnel_net_exit (4) Wang Liang
2025-10-20 12:54 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-12 21:35 syzbot
2025-10-18 10:48 ` syzbot
2025-10-25 4:55 ` 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=68f630ea.050a0220.91a22.0448.GAE@google.com \
--to=syzbot+3df59a64502c71cab3d5@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--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=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.