From: syzbot <syzbot+6641a61fe0e2e89ae8c5@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, sd@queasysnail.net,
steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in xfrm_state_fini (3)
Date: Tue, 29 Jul 2025 11:47:06 -0700 [thread overview]
Message-ID: <6889172a.a00a0220.26d0e1.000d.GAE@google.com> (raw)
In-Reply-To: <aIisBdRAM2vZ_VCW@krikkit>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+6641a61fe0e2e89ae8c5@syzkaller.appspotmail.com
Tested-by: syzbot+6641a61fe0e2e89ae8c5@syzkaller.appspotmail.com
Tested on:
commit: 86aa7218 Merge tag 'chrome-platform-v6.17' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16eb74a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6aef71a615d0cdf2
dashboard link: https://syzkaller.appspot.com/bug?extid=6641a61fe0e2e89ae8c5
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch: https://syzkaller.appspot.com/x/patch.diff?x=14b29782580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-07-29 18:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 7:08 [syzbot] [net?] WARNING in xfrm_state_fini (3) syzbot
2025-07-29 8:11 ` Hillf Danton
2025-07-29 9:05 ` syzbot
2025-07-29 11:01 ` Steffen Klassert
2025-07-29 11:09 ` Sabrina Dubroca
2025-07-29 18:47 ` syzbot [this message]
2025-08-28 11:06 ` Tetsuo Handa
2025-08-29 8:57 ` Sabrina Dubroca
2025-08-01 0:54 ` syzbot
[not found] <aIiYARi_eBdMAIhd@gauss3.secunet.de>
2025-07-29 9:44 ` syzbot
[not found] <aIiaPZa_jHAiuATa@gauss3.secunet.de>
2025-07-29 9: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=6889172a.a00a0220.26d0e1.000d.GAE@google.com \
--to=syzbot+6641a61fe0e2e89ae8c5@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=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 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.