[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJF2gTQH-cnTx_x3xO=UZRTrhewb0damO_cqtPxhxoZe6bxr8g@mail.gmail.com>
Date: Thu, 7 Apr 2022 14:33:17 +0800
From: Guo Ren <guoren@...nel.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Arnd Bergmann <arnd@...db.de>, Palmer Dabbelt <palmer@...belt.com>,
linux-arch <linux-arch@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-riscv <linux-riscv@...ts.infradead.org>,
Guo Ren <guoren@...ux.alibaba.com>,
Palmer Dabbelt <palmer@...osinc.com>,
Masami Hiramatsu <mhiramat@...nel.org>, stable@...r.kernel.org
Subject: Re: [PATCH V3] riscv: patch_text: Fixup last cpu should be master
On Thu, Apr 7, 2022 at 2:13 AM Greg KH <gregkh@...uxfoundation.org> wrote:
>
> On Wed, Apr 06, 2022 at 10:16:49PM +0800, guoren@...nel.org wrote:
> > From: Guo Ren <guoren@...ux.alibaba.com>
> >
> > These patch_text implementations are using stop_machine_cpuslocked
> > infrastructure with atomic cpu_count. The original idea: When the
> > master CPU patch_text, the others should wait for it. But current
> > implementation is using the first CPU as master, which couldn't
> > guarantee the remaining CPUs are waiting. This patch changes the
> > last CPU as the master to solve the potential risk.
> >
> > Signed-off-by: Guo Ren <guoren@...ux.alibaba.com>
> > Signed-off-by: Guo Ren <guoren@...nel.org>
> > Acked-by: Palmer Dabbelt <palmer@...osinc.com>
> > Reviewed-by: Masami Hiramatsu <mhiramat@...nel.org>
> > Cc: <stable@...r.kernel.org>
> > ---
> > arch/riscv/kernel/patch.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> What commit id does this change fix?
Thx for pointing this out, I would follow the rule to add Cc:
<stable@...r.kernel.org>.
>
--
Best Regards
Guo Ren
ML: https://lore.kernel.org/linux-csky/
Powered by blists - more mailing lists