From: Russell Coker <russell@coker.com.au>
To: "selinux-refpolicy@vger.kernel.org"
<selinux-refpolicy@vger.kernel.org>,
"Sugar, David" <dsugar@owlcyberdefense.com>
Subject: Re: fs_rw_tmpfs_files(fwupd_t)
Date: Sat, 13 Jun 2026 12:53:53 +1000 [thread overview]
Message-ID: <2386758.tgW7RDIVbh@xev> (raw)
In-Reply-To: <BNAP110MB2223F319362D6D91F04C86DEC218A@BNAP110MB2223.NAMP110.PROD.OUTLOOK.COM>
On Saturday, 13 June 2026 01:15:33 AEST Sugar, David wrote:
> The file in this case is a memfd file (created with memfd_create). You CAN
> transition this from tmpfs_t to a private type (i.e. fwupd_tmpfs_t). I
> just dealt with something like this for fapolicyd:
> https://github.com/SELinuxProject/refpolicy/pull/1141 Though I never saw
> denials for the create, the transition will work.
Thanks for the information.
This seems like a kernel bug. The domains in question aren't permitted to
create tmpfs_t objects but the domains in question can create them anyway.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
prev parent reply other threads:[~2026-06-13 2:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 14:27 fs_rw_tmpfs_files(fwupd_t) Russell Coker
2026-06-12 17:51 ` fs_rw_tmpfs_files(fwupd_t) Christopher J. PeBenito
[not found] ` <BNAP110MB2223F319362D6D91F04C86DEC218A@BNAP110MB2223.NAMP110.PROD.OUTLOOK.COM>
2026-06-13 2:53 ` Russell Coker [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=2386758.tgW7RDIVbh@xev \
--to=russell@coker.com.au \
--cc=dsugar@owlcyberdefense.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox