[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <30ab7555-8f36-cfb7-9101-0ebb92af3c2f@kernel.dk>
Date: Tue, 25 Apr 2023 13:12:36 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Junxiao Bi <junxiao.bi@...cle.com>, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org, linux-block@...r.kernel.org
Cc: paul@...l-moore.com, nathanl@...ux.ibm.com, jmorris@...ei.org,
serge@...lyn.com, konrad.wilk@...cle.com, joe.jin@...cle.com
Subject: Re: [PATCH V4 2/2] blktrace: allow access trace file in lockdown mode
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
Powered by blists - more mailing lists