From: Russell Coker <russell@coker.com.au>
To: SELinux Reference Policy mailing list
<selinux-refpolicy@vger.kernel.org>,
Chris PeBenito <pebenito@ieee.org>
Subject: Re: systemd and dontaudit
Date: Wed, 23 Jul 2025 22:57:56 +1000 [thread overview]
Message-ID: <12737856.O9o76ZdvQC@dojacat> (raw)
In-Reply-To: <2ee08e8f-59f4-418d-ab5e-01e0addaf17b@ieee.org>
On Wednesday, 23 July 2025 22:37:09 AEST Chris PeBenito wrote:
> On 7/22/2025 8:15 PM, Russell Coker wrote:
> > kernel_dontaudit_getattr_proc(systemd_logind_t)
> >
> > The above hides the fact that systemd-logind wants to statfs /proc and
> > that
> > can cause it to abort in some situations, to refuse to respond to dbus
> > requests, and to delay all logins by 25 seconds.
>
> Can you elaborate on what one of those failing situations is?
It only happened repeatedly on one of my systems. I think that triggering
that particular condition required multiple settings, so just not allowing
statfs isn't necessarily enough, some other combination of things allowed and
denied seemed necessary to get it into that state. The one system that had
this had it persist across reboots but other systems never had it. I had seen
it briefly happen on other systems but a reboot fixed it.
I didn't put as much effort into investigating this as I might have because
the access in question is fairly innocuous.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2025-07-23 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 0:15 systemd and dontaudit Russell Coker
2025-07-23 12:37 ` Chris PeBenito
2025-07-23 12:57 ` Russell Coker [this message]
2025-07-23 13:39 ` Dominick Grift
2025-07-23 14:29 ` Russell Coker
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=12737856.O9o76ZdvQC@dojacat \
--to=russell@coker.com.au \
--cc=pebenito@ieee.org \
--cc=selinux-refpolicy@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.