public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Tom Rix <trix@redhat.com>, Paul Menzel <pmenzel@molgen.mpg.de>,
	stable@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	llvm@lists.linux.dev
Subject: Re: Apply d799769188529abc6cbf035a10087a51f7832b6b to 5.17 and 5.15?
Date: Wed, 04 May 2022 13:19:32 +1000	[thread overview]
Message-ID: <87o80eugqj.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <YnGfyLAkB3NG+Ms2@dev-arch.thelio-3990X>

Nathan Chancellor <nathan@kernel.org> writes:
> On Thu, Apr 21, 2022 at 08:13:13AM -0700, Nathan Chancellor wrote:
>> On Thu, Apr 21, 2022 at 05:46:52PM +1000, Michael Ellerman wrote:
>> > Nathan Chancellor <nathan@kernel.org> writes:
>> > > Hi Greg, Sasha, and Michael,
>> > >
>> > > Commit d79976918852 ("powerpc/64: Add UADDR64 relocation support") fixes
>> > > a boot failure with CONFIG_RELOCATABLE=y kernels linked with recent
>> > > versions of ld.lld [1]. Additionally, it resolves a separate boot
>> > > failure that Paul Menzel reported [2] with ld.lld 13.0.0. Is this a
>> > > reasonable backport for 5.17 and 5.15? It applies cleanly, resolves both
>> > > problems, and does not appear to cause any other issues in my testing
>> > > for both trees but I was curious what Michael's opinion was, as I am far
>> > > from a PowerPC expert.
>> > >
>> > > This change does apply cleanly to 5.10 (I did not try earlier branches)
>> > > but there are other changes needed for ld.lld to link CONFIG_RELOCATABLE
>> > > kernels in that branch so to avoid any regressions, I think it is safe
>> > > to just focus on 5.15 and 5.17.
>> > 
>> > I considered tagging it for stable, but I wanted it to get a bit of
>> > testing first, it's a reasonably big patch.
>> > 
>> > I think we're reasonably confident it doesn't introduce any new bugs,
>> > but more testing time is always good.
>> > 
>> > So I guess I'd be inclined to wait another week or so before requesting
>> > a stable backport?
>> 
>> Sure, thanks for the response! I'll ping this thread on Monday, May 2nd,
>> so that we have two more RC releases to try and flush out any lingering
>> issues. If you do receive any reports of regressions, please let me
>> know.
>
> I decided to wait an extra day just to give people the opportunity to
> install -rc5 and run it through their tests. I have not heard of any
> reports yet, are there any further objections?

No objection.

cheers

  reply	other threads:[~2022-05-04  3:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 21:27 Apply d799769188529abc6cbf035a10087a51f7832b6b to 5.17 and 5.15? Nathan Chancellor
2022-04-21  7:46 ` Michael Ellerman
2022-04-21 15:13   ` Nathan Chancellor
2022-04-22  5:41     ` Michael Ellerman
2022-05-03 21:34     ` Nathan Chancellor
2022-05-04  3:19       ` Michael Ellerman [this message]
2022-05-04 15:07         ` Greg Kroah-Hartman

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=87o80eugqj.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=gregkh@linuxfoundation.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=trix@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox