From: Kees Cook <kees@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Ard Biesheuvel <ardb+git@google.com>,
linux-arm-kernel@lists.infradead.org, linux-efi@vger.kernel.org,
Ard Biesheuvel <ardb@kernel.org>, Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 1/2] lkdtm/bugs: Add cases for BUG and PANIC occurring in hardirq context
Date: Wed, 3 Dec 2025 10:02:56 -0800 [thread overview]
Message-ID: <202512031002.ED3098374@keescook> (raw)
In-Reply-To: <aR4ERqeHFbSWooZW@arm.com>
On Wed, Nov 19, 2025 at 05:54:14PM +0000, Catalin Marinas wrote:
> On Wed, Nov 12, 2025 at 06:53:18PM +0100, Ard Biesheuvel wrote:
> > From: Ard Biesheuvel <ardb@kernel.org>
> >
> > Add lkdtm cases to trigger a BUG() or panic() from hardirq context. This
> > is useful for testing pstore behavior being invoked from such contexts.
> >
> > Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> > ---
> > drivers/misc/lkdtm/bugs.c | 53 ++++++++++++++++++++
> > 1 file changed, 53 insertions(+)
>
> Kees, are you ok with this patch? Happy to take it through the arm64
> tree together with the second one.
With the small addition I just sent, yeah, this is fine by me. :)
Reviewed-by: Kees Cook <kees@kernel.org>
--
Kees Cook
next prev parent reply other threads:[~2025-12-03 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 17:53 [PATCH 0/2] efi/arm64: Simplify SVE/SME state preserve/restore Ard Biesheuvel
2025-11-12 17:53 ` [PATCH 1/2] lkdtm/bugs: Add cases for BUG and PANIC occurring in hardirq context Ard Biesheuvel
2025-11-19 17:54 ` Catalin Marinas
2025-12-03 18:02 ` Kees Cook [this message]
2025-12-03 18:02 ` Kees Cook
2025-11-12 17:53 ` [PATCH 2/2] arm64/efi: Remove unneeded SVE/SME fallback preserve/store handling Ard Biesheuvel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202512031002.ED3098374@keescook \
--to=kees@kernel.org \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).