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>, Paul Holzinger <pholzing@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] SELinux: Dontaudit access to dri devices
Date: Tue, 07 Apr 2026 11:11:11 +0200 (CEST)	[thread overview]
Message-ID: <20260407111110.4153e21b@elisabeth> (raw)
In-Reply-To: <adS_2Kr8pGSEAS23@suse.com>

On Tue, 7 Apr 2026 10:27:04 +0200
Johannes Segitz <jsegitz@suse.de> wrote:

> On Thu, Apr 02, 2026 at 03:36:58PM +0200, Paul Holzinger wrote:
> > I did a quick spot check in Podman and found a few places where a fd might
> > be leaked: https://github.com/containers/podman/pull/28434
> > 
> > That said I do not think any of these would explain an open /dev/dri path.  
> 
> I build podman with the change (and passt with the broader fd closing
> logic) and asked the reporter to test them. The denial is still shown with
> this unfortunately

Johannes, thanks for reporting back.

Paul, I was wondering: would there be a way to do something equivalent
to that close_range() directly in Podman, before it starts pasta? I
think it's a separate thread (or even a forked process) starting it,
but I haven't really checked.

-- 
Stefano


  reply	other threads:[~2026-04-07  9:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 11:05 Johannes Segitz
2026-03-30 15:15 ` Stefano Brivio
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-07  8:27           ` Johannes Segitz
2026-04-07  9:11             ` Stefano Brivio [this message]
2026-04-07 17:51               ` 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=20260407111110.4153e21b@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).