From: Greg KH <gregkh@linuxfoundation.org>
To: Yuan Tan <yuantan098@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: [STABLE] Backport requests for net/crypto fixes
Date: Thu, 7 May 2026 11:22:32 +0200 [thread overview]
Message-ID: <2026050731-copper-enactment-3ca4@gregkh> (raw)
In-Reply-To: <f0c6e3a5-2043-4611-9f6d-515aeb4922f6@gmail.com>
On Wed, May 06, 2026 at 11:07:50PM -0700, Yuan Tan wrote:
> [STABLE] Backport requests for net/crypto fixes
>
> Hi Linux stable team,
>
> Please consider backporting the following 3 upstream bug fixing commits to
> the relevant stable trees. After my inspection, they have not been
> backported.
>
> I am grouping these requests together for convenience. If you would prefer
> that I send one backport request per email, please let me know.
>
> MAINLINE_COMMIT MERGED_TO_MAINLINE_AT TITLE
> 629ec78ef8608d955ce217880cdc3e1873af3a15 2026-04-02T09:57:06-07:00 mpls: add seqcount to protect the platform_label{,s} pair
> 426c355742f02cf743b347d9d7dbdc1bfbfa31ef 2026-04-09T08:39:25-07:00 net: af_key: zero aligned sockaddr tail in PF_KEY exports
These both are in stable releases, what specific tree(s) do you want it
in?
> 01d798e9feb30212952d4e992801ba6bd6a82351 2026-04-15T15:22:26-07:00 crypto: jitterentropy - replace long-held spinlock with mutex
What kernel tree(s) do you want this in? Why was this not tagged for
stable already?
thanks,
greg k-h
next prev parent reply other threads:[~2026-05-07 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 6:07 [STABLE] Backport requests for net/crypto fixes Yuan Tan
2026-05-07 9:22 ` Greg KH [this message]
2026-05-09 0:26 ` Yuan Tan
2026-05-09 14:32 ` 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=2026050731-copper-enactment-3ca4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=yuantan098@gmail.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.