All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Guy Briggs <rgb@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: linux-security-module@vger.kernel.org, selinux@vger.kernel.org,
	linux-audit@redhat.com, io-uring@vger.kernel.org,
	linux-fsdevel@vger.kernel.org,
	Kumar Kartikeya Dwivedi <memxor@gmail.com>,
	Jens Axboe <axboe@kernel.dk>,
	Pavel Begunkov <asml.silence@gmail.com>
Subject: Re: [RFC PATCH v2 0/9] Add LSM access controls and auditing to io_uring
Date: Fri, 27 Aug 2021 09:35:59 -0400	[thread overview]
Message-ID: <20210827133559.GG490529@madcap2.tricolour.ca> (raw)
In-Reply-To: <CAHC9VhTkZ-tUdrFjhc2k1supzW1QJpY-15pf08mw6=ynU9yY5g@mail.gmail.com>

On 2021-08-26 15:14, Paul Moore wrote:
> On Thu, Aug 26, 2021 at 12:32 PM Richard Guy Briggs <rgb@redhat.com> wrote:
> > I'm getting:
> >         # ./iouring.2
> >         Kernel thread io_uring-sq is not running.
> >         Unable to setup io_uring: Permission denied
> >
> >         # ./iouring.3s
> >         >>> server started, pid = 2082
> >         >>> memfd created, fd = 3
> >         io_uring_queue_init: Permission denied
> >
> > I have CONFIG_IO_URING=y set, what else is needed?
> 
> I'm not sure how you tried to run those tests, but try running as root
> and with SELinux in permissive mode.

Ok, they ran, including iouring.4.  iouring.2 claimed twice: "Kernel
thread io_uring-sq is not running." and I didn't get any URING records
with ausearch.  I don't know if any of this is expected.

> paul moore

- RGB

--
Richard Guy Briggs <rgb@redhat.com>
Sr. S/W Engineer, Kernel Security, Base Operating Systems
Remote, Ottawa, Red Hat Canada
IRC: rgb, SunRaycer
Voice: +1.647.777.2635, Internal: (81) 32635


WARNING: multiple messages have this Message-ID (diff)
From: Richard Guy Briggs <rgb@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	selinux@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>,
	linux-security-module@vger.kernel.org, linux-audit@redhat.com,
	Kumar Kartikeya Dwivedi <memxor@gmail.com>,
	linux-fsdevel@vger.kernel.org, io-uring@vger.kernel.org
Subject: Re: [RFC PATCH v2 0/9] Add LSM access controls and auditing to io_uring
Date: Fri, 27 Aug 2021 09:35:59 -0400	[thread overview]
Message-ID: <20210827133559.GG490529@madcap2.tricolour.ca> (raw)
In-Reply-To: <CAHC9VhTkZ-tUdrFjhc2k1supzW1QJpY-15pf08mw6=ynU9yY5g@mail.gmail.com>

On 2021-08-26 15:14, Paul Moore wrote:
> On Thu, Aug 26, 2021 at 12:32 PM Richard Guy Briggs <rgb@redhat.com> wrote:
> > I'm getting:
> >         # ./iouring.2
> >         Kernel thread io_uring-sq is not running.
> >         Unable to setup io_uring: Permission denied
> >
> >         # ./iouring.3s
> >         >>> server started, pid = 2082
> >         >>> memfd created, fd = 3
> >         io_uring_queue_init: Permission denied
> >
> > I have CONFIG_IO_URING=y set, what else is needed?
> 
> I'm not sure how you tried to run those tests, but try running as root
> and with SELinux in permissive mode.

Ok, they ran, including iouring.4.  iouring.2 claimed twice: "Kernel
thread io_uring-sq is not running." and I didn't get any URING records
with ausearch.  I don't know if any of this is expected.

> paul moore

- RGB

--
Richard Guy Briggs <rgb@redhat.com>
Sr. S/W Engineer, Kernel Security, Base Operating Systems
Remote, Ottawa, Red Hat Canada
IRC: rgb, SunRaycer
Voice: +1.647.777.2635, Internal: (81) 32635

--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit


  reply	other threads:[~2021-08-27 13:36 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 20:48 [RFC PATCH v2 0/9] Add LSM access controls and auditing to io_uring Paul Moore
2021-08-11 20:48 ` Paul Moore
2021-08-11 20:48 ` [RFC PATCH v2 1/9] audit: prepare audit_context for use in calling contexts beyond syscalls Paul Moore
2021-08-11 20:48   ` Paul Moore
2021-08-11 20:48 ` [RFC PATCH v2 2/9] audit,io_uring,io-wq: add some basic audit support to io_uring Paul Moore
2021-08-11 20:48   ` [RFC PATCH v2 2/9] audit, io_uring, io-wq: " Paul Moore
2021-08-11 20:48 ` [RFC PATCH v2 3/9] audit: dev/test patch to force io_uring auditing Paul Moore
2021-08-11 20:48   ` Paul Moore
2021-08-11 20:48 ` [RFC PATCH v2 4/9] audit: add filtering for io_uring records Paul Moore
2021-08-11 20:48   ` Paul Moore
2021-08-11 20:48 ` [RFC PATCH v2 5/9] fs: add anon_inode_getfile_secure() similar to anon_inode_getfd_secure() Paul Moore
2021-08-11 20:48   ` Paul Moore
2021-08-12  9:32   ` Mickaël Salaün
2021-08-12  9:32     ` Mickaël Salaün
2021-08-12 14:32     ` Paul Moore
2021-08-12 14:32       ` Paul Moore
2021-08-12 15:35       ` Mickaël Salaün
2021-08-12 15:35         ` Mickaël Salaün
2021-08-11 20:48 ` [RFC PATCH v2 6/9] io_uring: convert io_uring to the secure anon inode interface Paul Moore
2021-08-11 20:48   ` Paul Moore
2021-08-11 20:48 ` [RFC PATCH v2 7/9] lsm,io_uring: add LSM hooks to io_uring Paul Moore
2021-08-11 20:48   ` Paul Moore
2021-08-11 20:49 ` [RFC PATCH v2 8/9] selinux: add support for the io_uring access controls Paul Moore
2021-08-11 20:49   ` Paul Moore
2021-08-11 20:49 ` [RFC PATCH v2 9/9] Smack: Brutalist io_uring support with debug Paul Moore
2021-08-11 20:49   ` Paul Moore
2021-08-31 14:44   ` Paul Moore
2021-08-31 14:44     ` Paul Moore
2021-08-31 15:03     ` Casey Schaufler
2021-08-31 15:03       ` Casey Schaufler
2021-08-31 16:43       ` Paul Moore
2021-08-31 16:43         ` Paul Moore
2021-08-24 20:57 ` [RFC PATCH v2 0/9] Add LSM access controls and auditing to io_uring Richard Guy Briggs
2021-08-24 20:57   ` Richard Guy Briggs
2021-08-24 22:27   ` Paul Moore
2021-08-24 22:27     ` Paul Moore
2021-08-25  1:36     ` Richard Guy Briggs
2021-08-25  1:36       ` Richard Guy Briggs
2021-08-26  1:16   ` Richard Guy Briggs
2021-08-26  1:16     ` Richard Guy Briggs
2021-08-26  1:34     ` Paul Moore
2021-08-26  1:34       ` Paul Moore
2021-08-26 16:32       ` Richard Guy Briggs
2021-08-26 16:32         ` Richard Guy Briggs
2021-08-26 19:14         ` Paul Moore
2021-08-26 19:14           ` Paul Moore
2021-08-27 13:35           ` Richard Guy Briggs [this message]
2021-08-27 13:35             ` Richard Guy Briggs
2021-08-27 19:49             ` Paul Moore
2021-08-27 19:49               ` Paul Moore
2021-08-28 15:03               ` Richard Guy Briggs
2021-08-28 15:03                 ` Richard Guy Briggs
2021-08-29 15:18                 ` Paul Moore
2021-08-29 15:18                   ` Paul Moore
2021-09-01 19:21                   ` Paul Moore
2021-09-01 19:21                     ` Paul Moore
2021-09-10  0:58                     ` Richard Guy Briggs
2021-09-10  0:58                       ` Richard Guy Briggs
2021-09-13 19:23                       ` Paul Moore
2021-09-13 19:23                         ` Paul Moore
2021-09-14  1:50                         ` Paul Moore
2021-09-14  1:50                           ` Paul Moore
2021-09-14  2:49                           ` Paul Moore
2021-09-14  2:49                             ` Paul Moore
2021-09-15 12:29                             ` Richard Guy Briggs
2021-09-15 12:29                               ` Richard Guy Briggs
2021-09-15 13:02                               ` Steve Grubb
2021-09-15 13:02                                 ` Steve Grubb
2021-09-15 14:12                               ` Paul Moore
2021-09-15 14:12                                 ` Paul Moore
2021-10-02 13:16                       ` Steve Grubb
2021-10-03 23:21                         ` Paul Moore
2021-10-04 12:39                           ` Richard Guy Briggs
2021-10-04 13:27                             ` Paul Moore
2021-10-04 14:59                               ` Steve Grubb
2021-10-28 20:07                                 ` Richard Guy Briggs

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=20210827133559.GG490529@madcap2.tricolour.ca \
    --to=rgb@redhat.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-audit@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=memxor@gmail.com \
    --cc=paul@paul-moore.com \
    --cc=selinux@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.