Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sabrina Dubroca <sd@queasysnail.net>
To: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>
Subject: Re: Patch "xfrm: propagate extack to all netlink doit handlers" has been added to the 5.10-stable tree
Date: Tue, 22 Sep 2026 09:49:41 +0200	[thread overview]
Message-ID: <arIzFfvyTnZnz-XZ@krikkit> (raw)
In-Reply-To: <20260921193130.1793731-1-sashal@kernel.org>

2026-09-21, 15:31:29 -0400, Sasha Levin wrote:
> This is a note to let you know that I've just added the patch titled
> 
>     xfrm: propagate extack to all netlink doit handlers
> 
> to the 5.10-stable tree which can be found at:
>     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

alongside:

xfrm: add extack to verify_sec_ctx_len
xfrm: add extack support to verify_newsa_info
xfrm: add extack to verify_one_alg, verify_auth_trunc, verify_aead
xfrm: avoid RCU warnings around the per-netns netlink socket

You're backporting all this stuff to avoid a completely trivial
conflict on the nlmsg_unicast call in the context for d1ebd9081879? :/

I'd say skip the backport if it's that much trouble, but of course
someone's LLM will come up with an "exploit" and a stupid name for the
bug. meh.

-- 
Sabrina

       reply	other threads:[~2026-09-22  7:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260921193130.1793731-1-sashal@kernel.org>
2026-09-22  7:49 ` Sabrina Dubroca [this message]
2026-09-22 15:39   ` Patch "xfrm: propagate extack to all netlink doit handlers" has been added to the 5.10-stable tree Sasha Levin
2026-09-23  8:51     ` Sabrina Dubroca

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=arIzFfvyTnZnz-XZ@krikkit \
    --to=sd@queasysnail.net \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /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