public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Johannes Segitz <jsegitz@suse.de>
Cc: passt-dev@passt.top, Paul Holzinger <pholzing@redhat.com>
Subject: Re: [PATCH] SELinux: Dontaudit access to dri devices
Date: Mon, 30 Mar 2026 17:15:42 +0200 (CEST)	[thread overview]
Message-ID: <20260330171541.15a8b5d0@elisabeth> (raw)
In-Reply-To: <20260330110557.2569119-1-jsegitz@suse.de>

[Adding Paul as he might know why this happens]

Hi Johannes,

On Mon, 30 Mar 2026 13:05:57 +0200
Johannes Segitz <jsegitz@suse.de> wrote:

> Currently podman can pass a FD to a DRI device to pasta, leading to AVCs
> like this:
> avc:  denied  { read write }
> comm="pasta" path="/dev/dri/renderD128"
> scontext=unconfined_u:unconfined_r:pasta_t:s0-s0:c0.c1023
> tcontext=system_u:object_r:dri_device_t:s0
> tclass=chr_file
> These are harmless, so dontaudit them
> 
> Signed-off-by: Johannes Segitz <jsegitz@suse.de>

Thanks for the patch.

I'm wondering how can this still happen though, as commit 09603cab28f9
("passt, util: Close any open file that the parent might have leaked")
should take care of those. Do you happen to know?

Perhaps the access happens before we call isolate_initial()... but then
I guess we should try to close leaked files before that point, to be on
the safe side?

-- 
Stefano


  reply	other threads:[~2026-03-30 15:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 11:05 Johannes Segitz
2026-03-30 15:15 ` Stefano Brivio [this message]
2026-03-31  7:00   ` Johannes Segitz
2026-03-31 19:47     ` Stefano Brivio
2026-04-01 12:12       ` Johannes Segitz
2026-04-02 12:24       ` Paul Holzinger
2026-04-02 13:36         ` Paul Holzinger
2026-04-02 13:46         ` Stefano Brivio
2026-04-02 14:07           ` Johannes Segitz

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=20260330171541.15a8b5d0@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=jsegitz@suse.de \
    --cc=passt-dev@passt.top \
    --cc=pholzing@redhat.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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).