linux-kernel - Re: [PATCH v2] lkdtm/bugs: add test for panic() with stuck secondary CPUs

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 for Android: free password hash cracker in your pocket

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

Message-Id: <169544125511.3844201.2326680356367331620.b4-ty@chromium.org>
Date:   Fri, 22 Sep 2023 20:54:18 -0700
From:   Kees Cook <keescook@...omium.org>
To:     linux-kernel@...r.kernel.org, Mark Rutland <mark.rutland@....com>
Cc:     Kees Cook <keescook@...omium.org>, dianders@...omium.org,
        sumit.garg@...aro.org, swboyd@...omium.org
Subject: Re: [PATCH v2] lkdtm/bugs: add test for panic() with stuck secondary CPUs

On Thu, 21 Sep 2023 17:16:34 +0100, Mark Rutland wrote:
> Upon a panic() the kernel will use either smp_send_stop() or
> crash_smp_send_stop() to attempt to stop secondary CPUs via an IPI,
> which may or may not be an NMI. Generally it's preferable that this is an
> NMI so that CPUs can be stopped in as many situations as possible, but
> it's not always possible to provide an NMI, and there are cases where
> CPUs may be unable to handle the NMI regardless.
> 
> [...]

I added a line to tests.tst and applied this to for-next/hardening, thanks!

[1/1] lkdtm/bugs: add test for panic() with stuck secondary CPUs
      https://git.kernel.org/kees/c/5fb07db970cf

Take care,

-- 
Kees Cook