From: Sabrina Dubroca <sd@queasysnail.net>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
syzbot <syzbot+6641a61fe0e2e89ae8c5@syzkaller.appspotmail.com>,
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, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in xfrm_state_fini (3)
Date: Fri, 29 Aug 2025 10:57:48 +0200 [thread overview]
Message-ID: <aLFrjEYwiEhaO5hK@krikkit> (raw)
In-Reply-To: <2a58b0b4-1c67-46d2-9c2a-fce3d26fc846@I-love.SAKURA.ne.jp>
2025-08-28, 20:06:29 +0900, Tetsuo Handa wrote:
> syzbot is still hitting this problem. Please check.
Thanks for the ping.
syzbot has found 2 different bugs that need separate fixes (but with
the same symptoms, hitting that WARNING, and coming from the same
patch series). I fixed one (syzbot confirmed the fix), I'm working on
the other one now.
> On 2025/07/29 20:09, Sabrina Dubroca wrote:
> >> Hi Sabrina, your recent ipcomp patches seem to trigger this issue.
> >> At least reverting them make it go away. Can you please look
> >> into this?
> >
> > I haven't looked at the other reports yet, but this one seems to be a
> > stupid mistake in my revert patch. With these changes, the syzbot
> > repro stops splatting here:
--
Sabrina
next prev parent reply other threads:[~2025-08-29 8:57 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
2025-08-28 11:06 ` Tetsuo Handa
2025-08-29 8:57 ` Sabrina Dubroca [this message]
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=aLFrjEYwiEhaO5hK@krikkit \
--to=sd@queasysnail.net \
--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=penguin-kernel@i-love.sakura.ne.jp \
--cc=steffen.klassert@secunet.com \
--cc=syzbot+6641a61fe0e2e89ae8c5@syzkaller.appspotmail.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.