public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Christian Brauner <brauner@kernel.org>
Cc: Linux Filesystem Development List <linux-fsdevel@vger.kernel.org>,
	fstests@vger.kernel.org, stable@vger.kernel.org,
	Leah Rumancik <leah.rumancik@gmail.com>,
	"Darrick J. Wong" <djwong@kernel.org>
Subject: Re: generic/645 failing on ext4, xfs (probably others) on all LTS kernels
Date: Fri, 15 Nov 2024 08:34:07 -0500	[thread overview]
Message-ID: <20241115133407.GB582565@mit.edu> (raw)
In-Reply-To: <20241111-tragik-busfahren-483825df1c00@brauner>

On Mon, Nov 11, 2024 at 09:52:07AM +0100, Christian Brauner wrote:

> behavior would be well-specified so the patch changed that quite some
> time ago.
> 
> Backporting this to older LTS kernels isn't difficult. We just need
> custom patches for the LTS kernels but they should all be very simple.
> 
> Alternatively, you can just ignore the test on older kernels.

Well, what the custom patch to look like wasn't obvious to me, but
that's because I'm not sufficiently familiar with the id mapping code.

So I'll just ignore the test on older kernels.  If someone wants to
create the custom patch, I'll revert the versioned exclude for
{kvm,gce}-xfsteests.

Thanks,

						- Ted


  reply	other threads:[~2024-11-15 13:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 18:05 generic/645 failing on ext4, xfs (probably others) on all LTS kernels Theodore Ts'o
2024-11-10 22:48 ` Matthew Wilcox
2024-11-11  8:52 ` Christian Brauner
2024-11-15 13:34   ` Theodore Ts'o [this message]
2024-11-15 15:21     ` Ojaswin Mujoo

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=20241115133407.GB582565@mit.edu \
    --to=tytso@mit.edu \
    --cc=brauner@kernel.org \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=leah.rumancik@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=stable@vger.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