From: Chris PeBenito <chpebeni@linux.microsoft.com>
To: Russell Coker <russell@coker.com.au>,
SELinux Reference Policy mailing list
<selinux-refpolicy@vger.kernel.org>
Cc: Paul Moore <paul@paul-moore.com>
Subject: Re: pidfs
Date: Mon, 9 Dec 2024 09:12:26 -0500 [thread overview]
Message-ID: <f8fc29de-d897-4e2b-aeb3-7f79f8036d30@linux.microsoft.com> (raw)
In-Reply-To: <1985778.PYKUYFuaPT@cupcakke>
On 12/6/2024 10:22 PM, Russell Coker wrote:
> What's this new pidfs that seems to have just become visible in 6.11.10 or
> similar recent kernels?
>
> https://lwn.net/Articles/714932/
>
> The above article has some information about a previous iteration of it,
> apparently not a separate mountable filesystem but a part of /proc that can be
> mounted as part of a container.
>
> I'm seeing the following audit entries about it, what should we do in policy
> about this?
>
> type=AVC msg=audit(1733540968.538:31305): avc: denied { getattr } for
> pid=1465 comm="systemd" name="/" dev="pidfs" ino=1
> scontext=etbe:user_r:user_systemd_t:s0-s0:c0.c1023
> tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem permissive=0
You should expect to see pidfds extensively with systemd processes, as
the main systemd interfaces now use pidfds.
Right now the only option is to use a genfscon or task sid. I'd have
preferred to improve the labeling behavior, but no kernel devs have had
a chance to address it.
See https://github.com/SELinuxProject/refpolicy/pull/762
--
Chris
prev parent reply other threads:[~2024-12-09 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 3:22 pidfs Russell Coker
2024-12-09 14:12 ` Chris PeBenito [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=f8fc29de-d897-4e2b-aeb3-7f79f8036d30@linux.microsoft.com \
--to=chpebeni@linux.microsoft.com \
--cc=paul@paul-moore.com \
--cc=russell@coker.com.au \
--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.