Linux kernel -stable discussions
 help / color / mirror / Atom feed
* [STABLE] Backport requests for net/crypto fixes
@ 2026-05-07  6:07 Yuan Tan
  2026-05-07  9:22 ` Greg KH
  0 siblings, 1 reply; 4+ messages in thread
From: Yuan Tan @ 2026-05-07  6:07 UTC (permalink / raw)
  To: stable; +Cc: yuantan098

[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
01d798e9feb30212952d4e992801ba6bd6a82351    2026-04-15T15:22:26-07:00    crypto: jitterentropy - replace long-held spinlock with mutex

Please let me know if you need any further information.

Thanks,
Yuan


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [STABLE] Backport requests for net/crypto fixes
  2026-05-07  6:07 [STABLE] Backport requests for net/crypto fixes Yuan Tan
@ 2026-05-07  9:22 ` Greg KH
  2026-05-09  0:26   ` Yuan Tan
  0 siblings, 1 reply; 4+ messages in thread
From: Greg KH @ 2026-05-07  9:22 UTC (permalink / raw)
  To: Yuan Tan; +Cc: stable

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [STABLE] Backport requests for net/crypto fixes
  2026-05-07  9:22 ` Greg KH
@ 2026-05-09  0:26   ` Yuan Tan
  2026-05-09 14:32     ` Sasha Levin
  0 siblings, 1 reply; 4+ messages in thread
From: Yuan Tan @ 2026-05-09  0:26 UTC (permalink / raw)
  To: Greg KH; +Cc: stable

On Thu, May 7, 2026 at 2:23 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> 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?

Regarding "mpls: add seqcount to protect the platform_label{,s} pair":
Both 6.12.y and 6.18.y are affected. However, our testing shows that
backporting results in code conflicts. We can send the resolved
patches later.

Regarding "net: af_key: zero aligned sockaddr tail in PF_KEY exports":
Our testing shows that the mainline patch can be backported to 6.12.y
and 6.18.y cleanly without any conflicts.

>
> > 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?

We have re-evaluated this bug and concluded that it requires root
privileges to trigger and has no security impact. Therefore, it does
not need to be backported.

Apologies for the confusion; we will improve our process next time.

>
> thanks,
>
> greg k-h

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [STABLE] Backport requests for net/crypto fixes
  2026-05-09  0:26   ` Yuan Tan
@ 2026-05-09 14:32     ` Sasha Levin
  0 siblings, 0 replies; 4+ messages in thread
From: Sasha Levin @ 2026-05-09 14:32 UTC (permalink / raw)
  To: Greg KH; +Cc: Sasha Levin, stable, Yuan Tan

> 2) 426c355742f0 ("net: af_key: zero aligned sockaddr tail in PF_KEY
>    exports") - targets 6.12.y and 6.18.y; cherry-pick is clean.

Queued for 6.12.y and 6.18.y, thanks.

> 1) 629ec78ef860 (mpls seqcount) - cherry-pick conflicts on 6.12/6.18;
>    I'll send manually-resolved patches later.

Sounds good, will look out for the resolved versions.

--
Thanks,
Sasha

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2026-05-09 14:32 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-07  6:07 [STABLE] Backport requests for net/crypto fixes Yuan Tan
2026-05-07  9:22 ` Greg KH
2026-05-09  0:26   ` Yuan Tan
2026-05-09 14:32     ` Sasha Levin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox