Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>,
	stable@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Tom Rix <trix@redhat.com>
Subject: Re: Patch "purgatory: fix disabling debug info" has been added to the 5.15-stable tree
Date: Tue, 18 Apr 2023 15:42:04 +0000	[thread overview]
Message-ID: <20230418154204.5eywuttjx2efukqq@x220> (raw)
In-Reply-To: <2023041837-dial-catchable-0203@gregkh>

[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]

On Tue, Apr 18, 2023 at 01:19:39PM +0200, Greg KH wrote:
> On Tue, Apr 18, 2023 at 10:39:51AM +0000, Alyssa Ross wrote:
> > On Mon, Apr 17, 2023 at 09:27:22PM -0400, Sasha Levin wrote:
> > > This is a note to let you know that I've just added the patch titled
> > >
> > >     purgatory: fix disabling debug info
> > >
> > > to the 5.15-stable tree which can be found at:
> > >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > >
> > > The filename of the patch is:
> > >      purgatory-fix-disabling-debug-info.patch
> > > and it can be found in the queue-5.15 subdirectory.
> > >
> > > If you, or anyone else, feels it should not be added to the stable tree,
> > > please let <stable@vger.kernel.org> know about it.
> >
> > There's no need for this patch on 5.15, as the regression it fixes was
> > only introduced in 6.0.
>
> Not according to the information in this commit, which says:
>
> Fixes: 32ef9e5054ec ("Makefile.debug: re-enable debug info for .S files")
>
> And that commit is in the following releases:
>
> 	4.19.264 5.4.221 5.10.152 5.15.76 5.19.12 6.0
>
> So it should be also in 5.4.y and 4.19.y, right?

Okay, it turns out that it should be included in 5.15.y and 5.10.y,
and I was missing it because unlike in 6.x, in 5.15.y and 5.10.y the
problem only affects Clang builds (using the integrated assembler),
since their versions of the commit in the Fixes tag are different to
the ones in 6.1.y and 6.2.y.

As you point out, 5.4.y and 4.19.y are also affected, and in fact
4.14.y is too.  But porting to these kernels is harder, because they
don't include 15d5761ad31d, which introduced asflags-remove-y.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-04-18 15:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230418012722.330253-1-sashal@kernel.org>
2023-04-18 10:39 ` Patch "purgatory: fix disabling debug info" has been added to the 5.15-stable tree Alyssa Ross
2023-04-18 11:18   ` Sasha Levin
2023-04-18 11:19   ` Greg KH
2023-04-18 15:42     ` Alyssa Ross [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=20230418154204.5eywuttjx2efukqq@x220 \
    --to=hi@alyssa.is \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=mingo@redhat.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=trix@redhat.com \
    --cc=x86@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