public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Paul Holzinger <pholzing@redhat.com>
Cc: passt-dev@passt.top, Max Chernoff <git@maxchernoff.ca>,
	Giuseppe Scrivano <gscrivan@redhat.com>,
	Lokesh Mandvekar <lmandvek@redhat.com>,
	Dan Walsh <dwalsh@redhat.com>
Subject: Re: [PATCH 1/2] selinux: add container_var_run_t type transition
Date: Thu, 18 Sep 2025 18:01:37 +0200	[thread overview]
Message-ID: <20250918180137.12749d7b@elisabeth> (raw)
In-Reply-To: <20250917120450.36181-2-pholzing@redhat.com>

On Wed, 17 Sep 2025 14:04:50 +0200
Paul Holzinger <pholzing@redhat.com> wrote:

> In some cases the podman runroot directory used to be labelled
> container_var_run_t instead of user_tmp_t which was expected here.
> Starting with a recent container-selinux change the runroot is now
> always container_var_run_t so make the policy handle both types to allow
> for a better upgrade path where passt-selinux and container-selinux are
> not updated at the same time.
> 
> Link: https://github.com/containers/container-selinux/pull/405
> Link: https://github.com/containers/podman/issues/26473
> 
> Signed-off-by: Paul Holzinger <pholzing@redhat.com>

Series applied, with all the changes as discussed. I'll make a release
soon so that container-selinux can proceed with container_var_run_t
as needed.

-- 
Stefano


  parent reply	other threads:[~2025-09-18 16:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17 12:04 Paul Holzinger
2025-09-17 12:04 ` [PATCH 2/2] selinux: add missing file contexts for Podman Paul Holzinger
2025-09-17 15:05   ` Stefano Brivio
2025-09-17 15:05 ` [PATCH 1/2] selinux: add container_var_run_t type transition Stefano Brivio
2025-09-17 15:54   ` Paul Holzinger
2025-09-18 16:01 ` Stefano Brivio [this message]
     [not found]   ` <CAFiEh0am6Pn7RGANe-0oQM-=-U=BXKD3afoRoefH4-3Ou1gVvA@mail.gmail.com>
2025-09-19 23:06     ` Stefano Brivio
2025-09-19 23:13       ` Stefano Brivio

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=20250918180137.12749d7b@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=dwalsh@redhat.com \
    --cc=git@maxchernoff.ca \
    --cc=gscrivan@redhat.com \
    --cc=lmandvek@redhat.com \
    --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).