Re: [PATCH V4 2/2] blktrace: allow access trace file in lockdown mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4/25/23 12:12 PM, Jens Axboe wrote:

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.

Thanks Jens. Lockdown is a security feature which is trying to limit user's(including root) capability to access security sensitive information inside kernel, there are two modes, read-only access is allowed in "integrity" mode while both read and write access are disabled in "confidentiality" mode.


Paul,  do you have any other concerns regarding blktrace? As Jens mentioned, blktrace just exported IO metadata to Userspace, those were not security sensitive information.

Thanks,

Junxiao.




[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux