On Wed, Sep 11, 2019 at 05:43:39AM -0400, Sasha Levin wrote:
> On Tue, Sep 10, 2019 at 12:26:54PM +0100, gregkh@xxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxx>.
> >
> > thanks,
> >
> > greg k-h
> >
> > ------------------ original commit in Linus's tree ------------------
> >
> > > From b9ee5e04fd77898208c51b1395fa0b5e8536f9b6 Mon Sep 17 00:00:00 2001
> > From: Christophe Leroy <christophe.leroy@xxxxxx>
> > 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
