From: Matthew Wilcox <willy@infradead.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Linux Filesystem Development List <linux-fsdevel@vger.kernel.org>,
fstests@vger.kernel.org, Christian Brauner <brauner@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: Sun, 10 Nov 2024 22:48:44 +0000 [thread overview]
Message-ID: <ZzE4TEPz5xuK6Y4M@casper.infradead.org> (raw)
In-Reply-To: <20241110180533.GA200429@mit.edu>
On Sun, Nov 10, 2024 at 01:05:33PM -0500, Theodore Ts'o wrote:
> (2) How much do we care that generic/645 is failing on LTS kernels?
> Are user/applications going to notice or care?
... if userspace applications won't notice this breakage, then why do we
run this test?
next prev parent reply other threads:[~2024-11-10 22:48 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 [this message]
2024-11-11 8:52 ` Christian Brauner
2024-11-15 13:34 ` Theodore Ts'o
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=ZzE4TEPz5xuK6Y4M@casper.infradead.org \
--to=willy@infradead.org \
--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 \
--cc=tytso@mit.edu \
/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