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] [day] [month] [year] [list]
Message-Id: <168860030768.22647.6698047675033569268.b4-ty@rivosinc.com>
Date:   Wed, 05 Jul 2023 16:38:27 -0700
From:   Palmer Dabbelt <palmer@...osinc.com>
To:     linux-kernel@...r.kernel.org, Marc Zyngier <maz@...nel.org>
Cc:     Conor Dooley <conor@...nel.org>,
        Anup Patel <apatel@...tanamicro.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] risc-v: Fix order of IPI enablement vs RCU startup


On Mon, 03 Jul 2023 19:31:26 +0100, Marc Zyngier wrote:
> Conor reports that risc-v tries to enable IPIs before telling the
> core code to enable RCU. With the introduction of the mapple tree
> as a backing store for the irq descriptors, this results in
> a very shouty boot sequence, as RCU is legitimately upset.
> 
> Restore some sanity by moving the risc_ipi_enable() call after
> notify_cpu_starting(), which explicitly enables RCU on the calling
> CPU.
> 
> [...]

Applied, thanks!

[1/1] risc-v: Fix order of IPI enablement vs RCU startup
      https://git.kernel.org/palmer/c/6259f3443c6a

Best regards,
-- 
Palmer Dabbelt <palmer@...osinc.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ