From: Sabrina Dubroca <sd@queasysnail.net>
To: Sasha Levin <sashal@kernel.org>, gregkh@linuxfoundation.org
Cc: stable@vger.kernel.org, Steffen Klassert <steffen.klassert@secunet.com>
Subject: Re: [PATCH 6.12.y 1/2] xfrm: delete x->tunnel as we delete x
Date: Tue, 29 Jul 2025 23:30:14 +0200 [thread overview]
Message-ID: <aIk9Zl0Fy4x8Z768@krikkit> (raw)
In-Reply-To: <20250729211153.2893984-1-sashal@kernel.org>
Hi Sasha/Greg,
2025-07-29, 17:11:52 -0400, Sasha Levin wrote:
> From: Sabrina Dubroca <sd@queasysnail.net>
>
> [ Upstream commit b441cf3f8c4b8576639d20c8eb4aa32917602ecd ]
2025-07-29, 17:11:53 -0400, Sasha Levin wrote:
> From: Sabrina Dubroca <sd@queasysnail.net>
>
> [ Upstream commit 2a198bbec6913ae1c90ec963750003c6213668c7 ]
Can you wait a bit before taking those 2 patches into stable? A couple
of syzbot reports landed today, one is definitely related to this
series [1], the others probably are as well [2][3]. The patches should
be dropped from all stable branches for now.
[1] https://lore.kernel.org/netdev/6888736f.a00a0220.b12ec.00ca.GAE@google.com/
[2] https://lore.kernel.org/netdev/68887370.a00a0220.b12ec.00cb.GAE@google.com/
[3] https://lore.kernel.org/netdev/68887370.a00a0220.b12ec.00cc.GAE@google.com/
Thanks,
--
Sabrina
next prev parent reply other threads:[~2025-07-29 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 14:32 FAILED: patch "[PATCH] Revert "xfrm: destroy xfrm_state synchronously on net exit" failed to apply to 6.12-stable tree gregkh
2025-07-29 21:11 ` [PATCH 6.12.y 1/2] xfrm: delete x->tunnel as we delete x Sasha Levin
2025-07-29 21:11 ` [PATCH 6.12.y 2/2] Revert "xfrm: destroy xfrm_state synchronously on net exit path" Sasha Levin
2025-07-29 21:30 ` Sabrina Dubroca [this message]
2025-07-29 22:46 ` [PATCH 6.12.y 1/2] xfrm: delete x->tunnel as we delete x Sasha Levin
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=aIk9Zl0Fy4x8Z768@krikkit \
--to=sd@queasysnail.net \
--cc=gregkh@linuxfoundation.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=steffen.klassert@secunet.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.