From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: christophe.leroy@c-s.fr, Chris.Packham@alliedtelesis.co.nz,
mpe@ellerman.id.au, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] powerpc/64e: Drop stale call to smp_processor_id() which" failed to apply to 4.19-stable tree
Date: Wed, 11 Sep 2019 10:48:12 +0100 [thread overview]
Message-ID: <20190911094812.GA13913@kroah.com> (raw)
In-Reply-To: <20190911094339.GL2012@sasha-vm>
On Wed, Sep 11, 2019 at 05:43:39AM -0400, Sasha Levin wrote:
> On Tue, Sep 10, 2019 at 12:26:54PM +0100, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 4.19-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> >
> > thanks,
> >
> > greg k-h
> >
> > ------------------ original commit in Linus's tree ------------------
> >
> > > From b9ee5e04fd77898208c51b1395fa0b5e8536f9b6 Mon Sep 17 00:00:00 2001
> > From: Christophe Leroy <christophe.leroy@c-s.fr>
> > Date: Thu, 8 Aug 2019 12:48:26 +0000
> > Subject: [PATCH] powerpc/64e: Drop stale call to smp_processor_id() which
> > hangs SMP startup
> >
> > Commit ebb9d30a6a74 ("powerpc/mm: any thread in one core can be the
> > first to setup TLB1") removed the need to know the cpu_id in
> > early_init_this_mmu(), but the call to smp_processor_id() which was
> > marked __maybe_used remained.
> >
> > Since commit ed1cd6deb013 ("powerpc: Activate CONFIG_THREAD_INFO_IN_TASK")
> > thread_info cannot be reached before MMU is properly set up.
> >
> > Drop this stale call to smp_processor_id() which makes SMP hang when
> > CONFIG_PREEMPT is set.
> >
> > Fixes: ebb9d30a6a74 ("powerpc/mm: any thread in one core can be the first to setup TLB1")
> > Fixes: ed1cd6deb013 ("powerpc: Activate CONFIG_THREAD_INFO_IN_TASK")
>
> Hi Greg,
>
> I *think* we should have our scripts parse multiple "Fixes:" tags as &&
> rather than ||.
Ah, crap, yes, you are right, I'll go fix my scripts...
greg k-h
prev parent reply other threads:[~2019-09-11 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 11:26 FAILED: patch "[PATCH] powerpc/64e: Drop stale call to smp_processor_id() which" failed to apply to 4.19-stable tree gregkh
2019-09-11 9:43 ` Sasha Levin
2019-09-11 9:48 ` Greg KH [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=20190911094812.GA13913@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=christophe.leroy@c-s.fr \
--cc=mpe@ellerman.id.au \
--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.