From: Hans Holmberg <Hans.Holmberg@wdc.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: "fstests@vger.kernel.org" <fstests@vger.kernel.org>,
"zlang@kernel.org" <zlang@kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Carlos Maiolino <cem@kernel.org>,
"djwong@kernel.org" <djwong@kernel.org>, hch <hch@lst.de>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"adilger.kernel@dilger.ca" <adilger.kernel@dilger.ca>
Subject: Re: [PATCH] ext4/002: make generic to support xfs
Date: Mon, 5 May 2025 09:20:28 +0000 [thread overview]
Message-ID: <8ea4ef50-cfda-46f1-a78e-eaff411de6f2@wdc.com> (raw)
In-Reply-To: <20250502133309.GB29583@mit.edu>
On 02/05/2025 15:33, Theodore Ts'o wrote:
> On Fri, May 02, 2025 at 11:35:01AM +0000, Hans Holmberg wrote:
>> xfs supports separate log devices and as this test now passes, share
>> it by turning it into a generic test.
>
> Was this fixed by a kernel commit to the XFS tree? If so, could you
> add a _fixed_by_kernel_commit pointing at the fix? And while you're
> at it, could you add:
>
>
> [ $FSTYP == "ext4" ] && \
> _fixed_by_kernel_commit 273108fa5015 \
> "ext4: handle read only external journal device"
>
> to the test? This will make it easier for people using LTS kernels to
> know which commits they need to backport.
>
> Many thanks!
>
> - Ted
The patch has been picked up in xfs for-next branch but it's not in
linus tree yet, so no stable commit hash for that yet.
I can add it in a v2, along with the ext4 fixed-commit once the xfsfix
is merged upstream.
Thanks!
prev parent reply other threads:[~2025-05-05 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 11:35 [PATCH] ext4/002: make generic to support xfs Hans Holmberg
2025-05-02 13:33 ` Theodore Ts'o
2025-05-05 9:20 ` Hans Holmberg [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=8ea4ef50-cfda-46f1-a78e-eaff411de6f2@wdc.com \
--to=hans.holmberg@wdc.com \
--cc=adilger.kernel@dilger.ca \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
--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