From: Kanchan Joshi <[email protected]>
To: Paul Moore <[email protected]>
Cc: Luis Chamberlain <[email protected]>,
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected]
Subject: Re: [PATCH] lsm,io_uring: add LSM hooks to for the new uring_cmd file op
Date: Sat, 16 Jul 2022 08:50:41 +0530 [thread overview]
Message-ID: <20220716032041.GB25618@test-zns> (raw)
In-Reply-To: <CAHC9VhQMABYKRqZmJQtXai0gtiueU42ENvSUH929=pF6tP9xOg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]
On Fri, Jul 15, 2022 at 02:46:16PM -0400, Paul Moore wrote:
>On Thu, Jul 14, 2022 at 9:00 PM Luis Chamberlain <[email protected]> wrote:
>> On Wed, Jul 13, 2022 at 11:00:42PM -0400, Paul Moore wrote:
>> > On Wed, Jul 13, 2022 at 8:05 PM Luis Chamberlain <[email protected]> wrote:
>> > >
>> > > io-uring cmd support was added through ee692a21e9bf ("fs,io_uring:
>> > > add infrastructure for uring-cmd"), this extended the struct
>> > > file_operations to allow a new command which each subsystem can use
>> > > to enable command passthrough. Add an LSM specific for the command
>> > > passthrough which enables LSMs to inspect the command details.
>> > >
>> > > This was discussed long ago without no clear pointer for something
>> > > conclusive, so this enables LSMs to at least reject this new file
>> > > operation.
>> > >
>> > > [0] https://lkml.kernel.org/r/[email protected]
>> >
>> > [NOTE: I now see that the IORING_OP_URING_CMD has made it into the
>> > v5.19-rcX releases, I'm going to be honest and say that I'm
>> > disappointed you didn't post the related LSM additions
>>
>> It does not mean I didn't ask for them too.
>>
>> > until
>> > v5.19-rc6, especially given our earlier discussions.]
>>
>> And hence since I don't see it either, it's on us now.
>
>It looks like I owe you an apology, Luis. While my frustration over
>io_uring remains, along with my disappointment that the io_uring
>developers continue to avoid discussing access controls with the LSM
>community, you are not the author of the IORING_OP_URING_CMD. You
I am to be shot down here. Solely.
My LSM understanding has been awful. At a level that I am not clear
how to fix if someone says - your code lacks LSM consideration.
But nothing to justify, I fully understand this is not someone else's
problem but mine. I intend to get better at it.
And I owe apology (to you/LSM-folks, Luis, Jens) for the mess.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2022-07-16 3:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 0:05 [PATCH] lsm,io_uring: add LSM hooks to for the new uring_cmd file op Luis Chamberlain
2022-07-14 0:38 ` Casey Schaufler
2022-07-15 0:54 ` Luis Chamberlain
2022-07-15 1:25 ` Casey Schaufler
2022-07-14 3:00 ` Paul Moore
2022-07-15 1:00 ` Luis Chamberlain
2022-07-15 18:46 ` Paul Moore
2022-07-15 19:02 ` Luis Chamberlain
2022-07-15 19:51 ` Paul Moore
2022-07-15 19:07 ` Jens Axboe
2022-07-15 19:50 ` Paul Moore
2022-07-15 20:00 ` Jens Axboe
2022-07-15 21:16 ` Casey Schaufler
2022-07-15 21:32 ` Jens Axboe
2022-07-15 21:37 ` Luis Chamberlain
2022-07-15 21:47 ` Jens Axboe
2022-07-15 20:50 ` Casey Schaufler
2022-07-15 23:03 ` Casey Schaufler
2022-07-15 23:05 ` Jens Axboe
2022-07-15 23:14 ` Casey Schaufler
2022-07-15 23:18 ` Jens Axboe
2022-07-15 23:31 ` Casey Schaufler
2022-07-15 23:34 ` Jens Axboe
2022-07-16 3:20 ` Kanchan Joshi [this message]
2022-07-18 14:55 ` Paul Moore
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=20220716032041.GB25618@test-zns \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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