All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Paul Moore <paul@paul-moore.com>
Cc: selinux@vger.kernel.org
Subject: Re: [PATCH 1/2] selinux: slow_avc_audit has become non-blocking
Date: Fri, 11 Jun 2021 01:45:01 +0000	[thread overview]
Message-ID: <YMLAHTAtjdgcvOl4@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <CAHC9VhSo5wPdqyZ2i9rWgZJhRCw3jv7aNuUFZBwJysFpAW7Drg@mail.gmail.com>

On Thu, Jun 10, 2021 at 07:12:15PM -0400, Paul Moore wrote:
> On Thu, Jun 10, 2021 at 11:51 AM Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > [followup to dump_common_audit_data() changes from this winter; in vfs.git#work.audit]
> > Does anybody have objections to the below?
> >
> > From 663a40ab49308b5acaba8a335190fce66e17d969 Mon Sep 17 00:00:00 2001
> > From: Al Viro <viro@zeniv.linux.org.uk>
> > Date: Sat, 16 Jan 2021 15:40:54 -0500
> > Subject: [PATCH 1/2] selinux: slow_avc_audit has become non-blocking
> >
> > dump_common_audit_data() is safe to use under rcu_read_lock() now;
> > no need for AVC_NONBLOCKING and games around it
> >
> > Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> > ---
> >  security/selinux/avc.c         | 28 ++++++++--------------------
> >  security/selinux/hooks.c       | 13 ++-----------
> >  security/selinux/include/avc.h |  4 ----
> >  3 files changed, 10 insertions(+), 35 deletions(-)
> 
> This looks okay to me, thanks Al.  If you want to fix patch 2/2 I can
> pull both into selinux/next.

Done and force-pushed into the same branch...  Do you want a formal pull request?

  reply	other threads:[~2021-06-11  1:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 15:51 [PATCH 1/2] selinux: slow_avc_audit has become non-blocking Al Viro
2021-06-10 15:52 ` [PATCH 2/2] kill unused 'flags' argument in avc_has_perm_flags() and avc_audit() Al Viro
2021-06-10 22:41   ` Paul Moore
2021-06-10 23:12 ` [PATCH 1/2] selinux: slow_avc_audit has become non-blocking Paul Moore
2021-06-11  1:45   ` Al Viro [this message]
2021-06-11  1:51     ` Paul Moore
2021-06-11 17:18       ` 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=YMLAHTAtjdgcvOl4@zeniv-ca.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --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.