From: "Daniel Walker (danielwa)" <danielwa@cisco.com>
To: Paul Moore <paul@paul-moore.com>
Cc: "Victor Kamensky (kamensky)" <kamensky@cisco.com>,
Eric Paris <eparis@redhat.com>,
"xe-linux-external(mailer list)" <xe-linux-external@cisco.com>,
"Ruslan Bilovol -X (rbilovol - GLOBALLOGIC INC at Cisco)"
<rbilovol@cisco.com>,
"linux-audit@redhat.com" <linux-audit@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] audit: show user land backtrace as part of audit context messages
Date: Tue, 2 Feb 2021 21:43:58 +0000 [thread overview]
Message-ID: <20210202214357.GD3710@zorba> (raw)
In-Reply-To: <CAHC9VhShkEJHWmuE2C_RLQy-Z3CpvAhTj68ki22v=AKF5hfvrQ@mail.gmail.com>
On Tue, Feb 02, 2021 at 04:35:42PM -0500, Paul Moore wrote:
> On Tue, Feb 2, 2021 at 4:29 PM Daniel Walker <danielwa@cisco.com> wrote:
> > From: Victor Kamensky <kamensky@cisco.com>
> >
> > To efficiently find out where SELinux AVC denial is comming from
> > take backtrace of user land process and display it as type=UBACKTRACE
> > message that comes as audit context for SELinux AVC and other audit
> > messages ...
>
> Have you tried the new perf tracepoint for SELinux AVC decisions that
> trigger an audit event? It's a new feature for v5.10 and looks to
> accomplish most of what you are looking for with this patch.
>
> * https://www.paul-moore.com/blog/d/2020/12/linux_v510.html
We haven't tried it, but I can look into it. We're not using v5.10 extensively
yet.
Daniel
next prev parent reply other threads:[~2021-02-02 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 21:29 Daniel Walker
2021-02-02 21:35 ` Paul Moore
2021-02-02 21:43 ` Daniel Walker (danielwa) [this message]
2021-02-02 21:45 ` Paul Moore
2021-02-02 22:11 ` Ondrej Mosnacek
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=20210202214357.GD3710@zorba \
--to=danielwa@cisco.com \
--cc=eparis@redhat.com \
--cc=kamensky@cisco.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=rbilovol@cisco.com \
--cc=xe-linux-external@cisco.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
all inboxes | Powered by JetHome®