From: Jens Axboe <axboe@kernel.dk>
To: Junxiao Bi <junxiao.bi@oracle.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-block@vger.kernel.org
Cc: paul@paul-moore.com, nathanl@linux.ibm.com, jmorris@namei.org,
serge@hallyn.com, konrad.wilk@oracle.com, joe.jin@oracle.com
Subject: Re: [PATCH V4 2/2] blktrace: allow access trace file in lockdown mode
Date: Tue, 25 Apr 2023 13:12:36 -0600 [thread overview]
Message-ID: <30ab7555-8f36-cfb7-9101-0ebb92af3c2f@kernel.dk> (raw)
In-Reply-To: <05b3eebd-7a3f-13d5-1fe9-8f4ab3080521@oracle.com>
On 4/25/23 11:55?AM, Junxiao Bi wrote:
> Any IO folks can help review this patch?
>
> Paul needs a confirm from you that the information blktrace exporting
> to userspace through the relay files are safe, not leaking information
> that userspace shouldn't know in lockdown mode.
I don't know anything about what lockdown is, but in terms of blktrace,
it is a way to trace meta data associated with IO. It'll tell you things
like "task T wants to {read,write} on device D, at offset X, and of size
Y". For passthrough IO, it'll also dump the CDB. There's never any
actual data traced.
--
Jens Axboe
next prev parent reply other threads:[~2023-04-25 19:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 21:53 [PATCH V4 1/2] debugfs: provide a way for relay user bypass lockdown Junxiao Bi
2023-04-20 21:53 ` [PATCH V4 2/2] blktrace: allow access trace file in lockdown mode Junxiao Bi
2023-04-25 17:55 ` Junxiao Bi
2023-04-25 19:12 ` Jens Axboe [this message]
2023-04-26 16:32 ` Junxiao Bi
2023-04-28 21:26 ` Paul Moore
2023-04-28 22:41 ` Junxiao Bi
2023-04-30 21:46 ` Paul Moore
2023-05-09 16:13 ` Junxiao Bi
2023-05-26 16:56 ` Junxiao Bi
2023-05-26 21:37 ` Paul Moore
2023-05-26 22:20 ` Junxiao Bi
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=30ab7555-8f36-cfb7-9101-0ebb92af3c2f@kernel.dk \
--to=axboe@kernel.dk \
--cc=jmorris@namei.org \
--cc=joe.jin@oracle.com \
--cc=junxiao.bi@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=nathanl@linux.ibm.com \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.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;
as well as URLs for NNTP newsgroup(s).