linux-kernel - Re: [PATCH V3] riscv: patch_text: Fixup last cpu should be master

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Yk3YUFfvEszb+cXT@kroah.com>
Date:   Wed, 6 Apr 2022 20:13:36 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     guoren@...nel.org
Cc:     arnd@...db.de, palmer@...belt.com, linux-arch@...r.kernel.org,
        linux-kernel@...r.kernel.org, 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 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?