[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f016d747-c01a-c46e-59a7-13d0d6306827@oracle.com>
Date: Fri, 28 Apr 2023 15:41:07 -0700
From: Junxiao Bi <junxiao.bi@...cle.com>
To: Paul Moore <paul@...l-moore.com>
Cc: Jens Axboe <axboe@...nel.dk>, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org, linux-block@...r.kernel.org,
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/28/23 2:26 PM, Paul Moore wrote:
> On Wed, Apr 26, 2023 at 12:33 PM Junxiao Bi <junxiao.bi@...cle.com> wrote:
>> 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.
> I think this version of the patchset is much better, thanks for your
> patience. I don't have any further concerns, and since the lockdown
> LSM doesn't have a dedicated maintainer I think you should be all set
> from my perspective.
Thanks a lot for the review.
>
> Since there are no changes under security/, I'm assuming this will go
> in via the tracing tree?
Should I notify some specific maintainer or mail list for merging?
Thanks,
Junxiao.
>
Powered by blists - more mailing lists