From: Stephen Smalley <stephen.smalley.work@gmail.com>
To: "Thiébaud Weksteen" <tweek@google.com>,
"Paul Moore" <paul@paul-moore.com>
Cc: Nick Kralevich <nnk@google.com>,
Joel Fernandes <joelaf@google.com>,
Peter Enderborg <peter.enderborg@sony.com>,
Eric Paris <eparis@parisplace.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, selinux@vger.kernel.org
Subject: Re: [PATCH v2 1/2] selinux: add tracepoint on denials
Date: Thu, 13 Aug 2020 11:41:48 -0400 [thread overview]
Message-ID: <15e2e26d-fe4b-679c-b5c0-c96d56e09853@gmail.com> (raw)
In-Reply-To: <20200813144914.737306-1-tweek@google.com>
On 8/13/20 10:48 AM, Thiébaud Weksteen wrote:
> The audit data currently captures which process and which target
> is responsible for a denial. There is no data on where exactly in the
> process that call occurred. Debugging can be made easier by being able to
> reconstruct the unified kernel and userland stack traces [1]. Add a
> tracepoint on the SELinux denials which can then be used by userland
> (i.e. perf).
>
> Although this patch could manually be added by each OS developer to
> trouble shoot a denial, adding it to the kernel streamlines the
> developers workflow.
>
> It is possible to use perf for monitoring the event:
> # perf record -e avc:selinux_audited -g -a
> ^C
> # perf report -g
> [...]
> 6.40% 6.40% audited=800000 tclass=4
> |
> __libc_start_main
> |
> |--4.60%--__GI___ioctl
> | entry_SYSCALL_64
> | do_syscall_64
> | __x64_sys_ioctl
> | ksys_ioctl
> | binder_ioctl
> | binder_set_nice
> | can_nice
> | capable
> | security_capable
> | cred_has_capability.isra.0
> | slow_avc_audit
> | common_lsm_audit
> | avc_audit_post_callback
> | avc_audit_post_callback
> |
>
> It is also possible to use the ftrace interface:
> # echo 1 > /sys/kernel/debug/tracing/events/avc/selinux_audited/enable
> # cat /sys/kernel/debug/tracing/trace
> tracer: nop
> entries-in-buffer/entries-written: 1/1 #P:8
> [...]
> dmesg-3624 [001] 13072.325358: selinux_denied: audited=800000 tclass=4
An explanation here of how one might go about decoding audited and
tclass would be helpful to users (even better would be a script to do it
for them). Again, I know how to do that but not everyone using
perf/ftrace will.
next prev parent reply other threads:[~2020-08-13 15:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 14:48 Thiébaud Weksteen
2020-08-13 14:48 ` [PATCH v2 2/2] selinux: add basic filtering for audit trace events Thiébaud Weksteen
2020-08-13 15:05 ` Casey Schaufler
2020-08-13 15:35 ` peter enderborg
2020-08-13 15:49 ` Stephen Smalley
2020-08-13 16:10 ` peter enderborg
2020-08-13 17:14 ` peter enderborg
2020-08-13 17:38 ` Steven Rostedt
2020-08-13 18:18 ` peter enderborg
2020-08-13 19:16 ` Steven Rostedt
2020-08-13 15:41 ` Stephen Smalley [this message]
2020-08-14 13:05 ` [PATCH v2 1/2] selinux: add tracepoint on denials Thiébaud Weksteen
2020-08-14 16:51 ` Stephen Smalley
2020-08-14 17:07 ` peter enderborg
2020-08-14 17:08 ` Stephen Smalley
2020-08-14 17:22 ` peter enderborg
2020-08-14 17:46 ` Steven Rostedt
2020-08-14 18:06 ` peter enderborg
2020-08-14 18:30 ` Steven Rostedt
2020-08-14 18:50 ` peter enderborg
2020-08-14 18:56 ` Steven Rostedt
2020-08-15 7:17 ` peter enderborg
2020-08-15 8:45 ` peter enderborg
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=15e2e26d-fe4b-679c-b5c0-c96d56e09853@gmail.com \
--to=stephen.smalley.work@gmail.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=eparis@parisplace.org \
--cc=joelaf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mingo@redhat.com \
--cc=nnk@google.com \
--cc=paul@paul-moore.com \
--cc=peter.enderborg@sony.com \
--cc=robh@kernel.org \
--cc=rostedt@goodmis.org \
--cc=selinux@vger.kernel.org \
--cc=tweek@google.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®