From: Jakub Kicinski <kuba@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, James Chapman <jchapman@katalix.com>,
regressions@lists.linux.dev
Subject: Re: Kernel panics trying to set up L2TP VPN (`__xfrm_state_destroy+0x6e/0x80`)
Date: Mon, 6 Oct 2025 11:58:12 -0700 [thread overview]
Message-ID: <20251006115812.7408e8e9@kernel.org> (raw)
In-Reply-To: <b353f7e5-c32a-4f91-acbc-2b7aaa64c28f@molgen.mpg.de>
On Mon, 6 Oct 2025 08:37:06 +0200 Paul Menzel wrote:
> #regzbot introduced: v6.17..070a542f08ac
Nothing obvious in this range. Could you bisect?
On xfrm side only c829aab21ed55 stands out but it's not too complex
either.
next prev parent reply other threads:[~2025-10-06 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 6:37 Kernel panics trying to set up L2TP VPN (`__xfrm_state_destroy+0x6e/0x80`) Paul Menzel
2025-10-06 7:05 ` Paul Menzel
2025-10-06 18:58 ` Jakub Kicinski [this message]
2025-11-01 10:46 ` Paul Menzel
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=20251006115812.7408e8e9@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jchapman@katalix.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=regressions@lists.linux.dev \
/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).