From: Junxiao Bi <junxiao.bi@oracle.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-block@vger.kernel.org, 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: Fri, 28 Apr 2023 15:41:07 -0700 [thread overview]
Message-ID: <f016d747-c01a-c46e-59a7-13d0d6306827@oracle.com> (raw)
In-Reply-To: <CAHC9VhT2uCc5ePi+ung+rLaDiLCCCF=fjq8G+D3FJf0i4E8_hQ@mail.gmail.com>
On 4/28/23 2:26 PM, Paul Moore wrote:
> On Wed, Apr 26, 2023 at 12:33 PM Junxiao Bi <junxiao.bi@oracle.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.
>
next prev parent reply other threads:[~2023-04-28 22:41 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
2023-04-26 16:32 ` Junxiao Bi
2023-04-28 21:26 ` Paul Moore
2023-04-28 22:41 ` Junxiao Bi [this message]
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=f016d747-c01a-c46e-59a7-13d0d6306827@oracle.com \
--to=junxiao.bi@oracle.com \
--cc=axboe@kernel.dk \
--cc=jmorris@namei.org \
--cc=joe.jin@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).