From: Paul Moore <paul@paul-moore.com>
To: John Johansen <john.johansen@canonical.com>
Cc: Andreas Steinmetz <anstein99@googlemail.com>,
apparmor@lists.ubuntu.com, audit@vger.kernel.org
Subject: Re: [apparmor] AppArmor kernel audit locks up system
Date: Wed, 18 Oct 2023 18:23:20 -0400 [thread overview]
Message-ID: <CAHC9VhTE+xCnAj-NXgCZJwYkp9i1KAJCgQDPWjE3msVYScTQCg@mail.gmail.com> (raw)
In-Reply-To: <CAHC9VhQ_i0TnA+Snsg-gsPEEb=uHyiNKDm48jmiuRc7y1-Gd=Q@mail.gmail.com>
On Wed, Oct 18, 2023 at 5:00 PM Paul Moore <paul@paul-moore.com> wrote:
> On Wed, Oct 18, 2023 at 4:50 PM Paul Moore <paul@paul-moore.com> wrote:
> > It shouldn't, the only time we ever really operate on something other
> > than @current is when a fork/clone happens and we are filtering on the
> > new child process. At least that used to be the case, I can't imagine
> > someone would audit something other than @current (not sure you could
> > with respect to this stuff?), but I guess it couldn't hurt to double
> > check on the current code base.
>
> Yes, that still looks to be the case.
>
> --
> paul-moore.com
Patch posting:
https://lore.kernel.org/audit/20231018222023.371274-2-paul@paul-moore.com
--
paul-moore.com
prev parent reply other threads:[~2023-10-18 22:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOTMNwuhq9Fc1PW4Y6ZOyP8H7nCk3+9gsxRapRuScZ2-a+14hA@mail.gmail.com>
2023-09-27 12:20 ` [apparmor] AppArmor kernel audit locks up system John Johansen
2023-10-07 0:07 ` Paul Moore
2023-10-09 6:39 ` Andreas Steinmetz
2023-10-09 17:06 ` Paul Moore
2023-10-09 17:41 ` John Johansen
2023-10-09 17:51 ` Paul Moore
2023-10-18 20:03 ` Paul Moore
2023-10-18 20:34 ` John Johansen
2023-10-18 20:50 ` Paul Moore
2023-10-18 21:00 ` Paul Moore
2023-10-18 22:23 ` 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=CAHC9VhTE+xCnAj-NXgCZJwYkp9i1KAJCgQDPWjE3msVYScTQCg@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=anstein99@googlemail.com \
--cc=apparmor@lists.ubuntu.com \
--cc=audit@vger.kernel.org \
--cc=john.johansen@canonical.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 read-only IMAP folder(s) and NNTP newsgroup(s).