Linux filesystem development
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Mario Limonciello <superm1@kernel.org>
Cc: Linux kernel regressions list <regressions@lists.linux.dev>,
	 David Howells <dhowells@redhat.com>,
	linux-fsdevel@vger.kernel.org, yaneti@declera.com
Subject: Re: distrobox / podman / toolbox not working anymore with 6.15-rc1
Date: Tue, 8 Apr 2025 10:16:23 +0200	[thread overview]
Message-ID: <20250408-tonart-unkommentiert-1525c590f79b@brauner> (raw)
In-Reply-To: <9a6af7c9-bc77-4bcf-8a4c-2aea712ede25@kernel.org>

On Mon, Apr 07, 2025 at 03:54:17PM -0500, Mario Limonciello wrote:
> On 4/7/2025 10:48 AM, Mario Limonciello wrote:
> > Hello,
> > 
> > With upgrading to 6.15-rc1, the tools in the subject have stopped
> > working [1].  The following error is encountered when trying to enter a
> > container (reproduced using distrobox)
> > 
> > crun: chown /dev/pts/0: Operation not permitted: OCI permission denied
> > 
> > This has been root caused to:
> > 
> > commit cc0876f817d6d ("vfs: Convert devpts to use the new mount API")
> > 
> > Reverting this commit locally fixes the issue.
> > 
> > Link: https://github.com/89luca89/distrobox/issues/1722 [1]
> > 
> > Thanks,
> > 
> 
> David shared this on the Github thread:
> 
> https://lore.kernel.org/linux-fsdevel/759134.1743596274@warthog.procyon.org.uk/
> 
> I can confirm it fixes the issue.

The fix will go upstream this today or tomorrow. It's in -next
currently.

      reply	other threads:[~2025-04-08  8:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 15:48 distrobox / podman / toolbox not working anymore with 6.15-rc1 Mario Limonciello
2025-04-07 20:54 ` Mario Limonciello
2025-04-08  8:16   ` Christian Brauner [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=20250408-tonart-unkommentiert-1525c590f79b@brauner \
    --to=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=superm1@kernel.org \
    --cc=yaneti@declera.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox