All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominick Grift <dominick.grift@defensec.nl>
To: Russell Coker <russell@coker.com.au>
Cc: selinux-refpolicy@vger.kernel.org
Subject: Re: /dev/full
Date: Mon, 28 Sep 2026 06:28:27 +0200	[thread overview]
Message-ID: <87ld8m3spg.fsf@defensec.nl> (raw)
In-Reply-To: <E0Chzh_JRYWsdztEXSLhhQ@coker.com.au> (Russell Coker's message of "Mon, 28 Sep 2026 11:28:48 +1000")

Russell Coker <russell@coker.com.au> writes:

> Running a recent Debian kernel with latest git policy without the unconfined 
> module I'm seeing the following.  Why would /dev/full be getting the wrong 
> label early in the boot?  It gets fixed along the way somewhere before the 
> system goes to multi-user mode.
>
> # dmesg|grep event_device_t
> [   11.282465] audit: type=1400 audit(1790509173.037:4): avc:  denied  { write 
> } for  pid=534 comm="modprobe" name="full" dev="devtmpfs" ino=7 
> scontext=system_u:system_r:kmod_t:s0 
> tcontext=system_u:object_r:event_device_t:s0 tclass=chr_file permissive=0
> # ls -lZi /dev/full
> 7 crw-rw-rw-. 1 root root system_u:object_r:null_device_t:s0 1, 7 Sep 27 21:39 
> /dev/full
> # uname -a
> Linux babycakes 7.2.8+deb14-amd64 #1 SMP PREEMPT_DYNAMIC Debian 7.2.8-1 
> (2026-09-26) x86_64 GNU/Linux

I noticed similar. I suspect this is due to how userspace_initial_sid
polcap is implemented in refpolicy (refpolicy does leverage it does it
not?). Misssing an appropriate auto type transition because the scenario
changed.


-- 
gpg --auto-key-locate clear,nodefault,wkd --locate-external-keys dominick.grift@defensec.nl
Key fingerprint = FCD2 3660 5D6B 9D27 7FC6  E0FF DA7E 521F 10F6 4098
Dominick Grift
Mastodon: @kcinimod@defensec.nl

  reply	other threads:[~2026-09-28  4:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28  1:28 /dev/full Russell Coker
2026-09-28  4:28 ` Dominick Grift [this message]
2026-09-28 10:09   ` /dev/full Russell Coker
2026-09-28 10:20     ` /dev/full Dominick Grift
2026-09-28 10:34       ` /dev/full Dominick Grift
2026-09-28 11:58         ` /dev/full Russell Coker
2026-09-28 12:10           ` /dev/full Russell Coker
2026-09-28 12:21             ` /dev/full Dominick Grift
2026-09-28 13:18               ` /dev/full Russell Coker
2026-09-28 13:34                 ` /dev/full Dominick Grift

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=87ld8m3spg.fsf@defensec.nl \
    --to=dominick.grift@defensec.nl \
    --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.