On Thu, Apr 7, 2022 at 2:13 AM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > On Wed, Apr 06, 2022 at 10:16:49PM +0800, guoren@xxxxxxxxxx wrote: > > From: Guo Ren <guoren@xxxxxxxxxxxxxxxxx> > > > > 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@xxxxxxxxxxxxxxxxx> > > Signed-off-by: Guo Ren <guoren@xxxxxxxxxx> > > Acked-by: Palmer Dabbelt <palmer@xxxxxxxxxxxx> > > Reviewed-by: Masami Hiramatsu <mhiramat@xxxxxxxxxx> > > Cc: <stable@xxxxxxxxxxxxxxx> > > --- > > 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@xxxxxxxxxxxxxxx>. > -- Best Regards Guo Ren ML: https://lore.kernel.org/linux-csky/
