From: Daniel Wagner <dwagner@suse.de>
To: Disha Goel <disgoel@linux.ibm.com>
Cc: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
linux-block@vger.kernel.org
Subject: Re: [PATCH blktests] blktrace/001: Skip test when kernel lockdown is enabled
Date: Mon, 11 May 2026 09:58:44 +0200 [thread overview]
Message-ID: <953e383a-b9ce-4ef6-a471-5d91aa7eda88@flourine.local> (raw)
In-Reply-To: <1621bb15-b425-42d8-9ced-b3886dce1060@linux.ibm.com>
Hi Disha,
On Mon, May 11, 2026 at 01:16:03PM +0530, Disha Goel wrote:
> Thank you for pointing me to the SUSE lockdown patches. After analysing
> them, I found that the second patch (lockdown-fix-kernel-lockdown-
> enforcement-issue-when-secure.patch) is causing the issue.
>
> This patch fixes bsc#1237521 by directly calling lockdown hooks, but it
> appears to be too restrictive - it blocks blktrace from accessing
> debugfs even though upstream kernel 7.1+ allows this with lockdown
> enabled.
Right, so it's a downstream problem as expected.
> The patch works around a timing issue but has the side effect of
> blocking legitimate debugging tools. Is this intentional, or should
> debugging tools like blktrace be allowed even with lockdown enabled?
I am not really involved into this part of our downstream kernel and
don't know why these patches didn't make it upstream :)
Would you mind to you create a SUSE bugzilla issue and we can figure out
a solution there?
Thanks a lot!
Daniel
next prev parent reply other threads:[~2026-05-11 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 14:11 [PATCH blktests] blktrace/001: Skip test when kernel lockdown is enabled Disha Goel
2026-04-29 13:52 ` Shin'ichiro Kawasaki
2026-05-08 11:21 ` Disha Goel
2026-05-08 17:39 ` Daniel Wagner
2026-05-11 7:46 ` Disha Goel
2026-05-11 7:58 ` Daniel Wagner [this message]
2026-05-09 10:35 ` Shin'ichiro Kawasaki
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=953e383a-b9ce-4ef6-a471-5d91aa7eda88@flourine.local \
--to=dwagner@suse.de \
--cc=disgoel@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
/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