From: Paul Moore <paul@paul-moore.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH v3 8/8] Smack: Brutalist io_uring support with debug
Date: Tue, 14 Sep 2021 10:44:46 -0400 [thread overview]
Message-ID: <CAHC9VhSW5EEyAyLAhaEHh2iu++doCZ3L1jsEZjMoW_c4uFn3Lg@mail.gmail.com> (raw)
In-Reply-To: <959ac399-24a9-6267-7c4d-40789ffd1a41@schaufler-ca.com>
On Tue, Sep 14, 2021 at 10:26 AM Casey Schaufler <casey@schaufler-ca.com> wrote:
>
> On 9/13/2021 8:33 PM, Paul Moore wrote:
> > From: Casey Schaufler <casey@schaufler-ca.com>
> >
> > Add Smack privilege checks for io_uring. Use CAP_MAC_OVERRIDE
> > for the override_creds case and CAP_MAC_ADMIN for creating a
> > polling thread. These choices are based on conjecture regarding
> > the intent of the surrounding code.
> >
> > Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
> > [PM: make the smack_uring_* funcs static, remove debug code]
> > Signed-off-by: Paul Moore <paul@paul-moore.com>
>
> You want to change the subject:
>
> [PATCH v3 8/8] Smack: Brutalist io_uring support with debug
>
> s/ with debug//
Thanks Casey, good catch. I updated my local copy and the
selinux/working-io_uring branch but I'll refrain from pushing a new
patchset just for this.
--
paul moore
www.paul-moore.com
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2021-09-14 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 3:32 [PATCH v3 0/8] Add LSM access controls and auditing to io_uring Paul Moore
2021-09-14 3:32 ` [PATCH v3 1/8] audit: prepare audit_context for use in calling contexts beyond syscalls Paul Moore
2021-09-14 3:33 ` [PATCH v3 2/8] audit, io_uring, io-wq: add some basic audit support to io_uring Paul Moore
2021-09-14 3:33 ` [PATCH v3 3/8] audit: add filtering for io_uring records Paul Moore
2021-09-14 3:33 ` [PATCH v3 4/8] fs: add anon_inode_getfile_secure() similar to anon_inode_getfd_secure() Paul Moore
2021-09-14 3:33 ` [PATCH v3 5/8] io_uring: convert io_uring to the secure anon inode interface Paul Moore
2021-09-14 3:33 ` [PATCH v3 6/8] lsm,io_uring: add LSM hooks to io_uring Paul Moore
2021-09-14 3:33 ` [PATCH v3 7/8] selinux: add support for the io_uring access controls Paul Moore
2021-09-14 3:33 ` [PATCH v3 8/8] Smack: Brutalist io_uring support with debug Paul Moore
2021-09-14 14:26 ` Casey Schaufler
2021-09-14 14:44 ` Paul Moore [this message]
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=CAHC9VhSW5EEyAyLAhaEHh2iu++doCZ3L1jsEZjMoW_c4uFn3Lg@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=casey@schaufler-ca.com \
--cc=linux-audit@redhat.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).