All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
	stable@vger.kernel.org,
	Nick Desaulniers <ndesaulniers@google.com>,
	Marcus Seyfarth <m.seyfarth@gmail.com>
Subject: Re: Please apply 90dfeef1cd38 to 6.1 through 6.18
Date: Sat, 25 Jul 2026 07:17:49 +0200	[thread overview]
Message-ID: <2026072534-strife-astronomy-3122@gregkh> (raw)
In-Reply-To: <20260725011342.GA2792705@ax162>

On Fri, Jul 24, 2026 at 06:13:42PM -0700, Nathan Chancellor wrote:
> Hi stable folks,
> 
> Upstream commit cc39f3872c08 ("seqlock: Introduce
> scoped_seqlock_read()") was backported in several stable branches (6.18
> through 6.1) recently without a necessary fix, commit 90dfeef1cd38
> ("seqlock: Cure some more scoped_seqlock() optimization fails"),
> breaking the build for certain configurations
> 
>   https://github.com/ClangBuiltLinux/linux/issues/2178
> 
> Please consider applying 90dfeef1cd38 to 6.18 through 6.1 to avoid this,
> it applies cleanly to all those trees for me. You may also want to
> consider taking
> 
>   b94d45b6bbb4 ("seqlock: Allow KASAN to fail optimizing")
>   88331c4ec23a ("seqlock: Allow UBSAN_ALIGNMENT to fail optimizing")
> 
> but I did not test if they were clean cherry picks.

they do seem clean, so I've taken them all now, thanks!

greg k-h

      reply	other threads:[~2026-07-25  5:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-25  1:13 Please apply 90dfeef1cd38 to 6.1 through 6.18 Nathan Chancellor
2026-07-25  5:17 ` Greg Kroah-Hartman [this message]

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=2026072534-strife-astronomy-3122@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=m.seyfarth@gmail.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --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 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.