Linux filesystem development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	Amir Goldstein <amir73il@gmail.com>,
	Zorro Lang <zlang@kernel.org>,
	linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	fstests@vger.kernel.org
Subject: Re: [PATCH 0/2] Support overlayfs in the idmapped mount tests
Date: Thu, 9 Jul 2026 22:33:46 -0700	[thread overview]
Message-ID: <alCEOvHNDOfRHySm@infradead.org> (raw)
In-Reply-To: <20260615-overlay-idmapped-vfstest-v1-0-c6b3b2228092@kernel.org>

On Mon, Jun 15, 2026 at 05:33:28PM +0200, Christian Brauner wrote:
> This change is required to make the series in [1] which makes idmapped
> overlayfs mounts work compatible with the idmapped mount test suite.
> 
> The vfstest idmapped mount tests behind generic/633, generic/696 and
> generic/697 fail on overlayfs for two reasons that are specific to
> overlayfs and unrelated to idmapped mount semantics:

They also fail on just testing XFS for me now that the commit has
landed, so this description is a little confusing.  As is the patch
series title.


      parent reply	other threads:[~2026-07-10  5:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-15 15:33 [PATCH 0/2] Support overlayfs in the idmapped mount tests Christian Brauner
2026-06-15 15:33 ` [PATCH 1/2] src/vfs: probe O_TMPFILE support on the base mount in the idmapped tests Christian Brauner
2026-06-15 17:53   ` Amir Goldstein
2026-07-10  5:34   ` Christoph Hellwig
2026-06-15 15:33 ` [PATCH 2/2] src/vfs: skip whiteout-device fixtures on overlayfs Christian Brauner
2026-06-15 18:03   ` Amir Goldstein
2026-07-10  5:34     ` Christoph Hellwig
2026-07-10  5:33 ` Christoph Hellwig [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=alCEOvHNDOfRHySm@infradead.org \
    --to=hch@infradead.org \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=zlang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox