From: Zorro Lang <zlang@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] shared/298: run xfs_db against the loop device instead of the image file
Date: Sun, 3 Mar 2024 22:41:47 +0800 [thread overview]
Message-ID: <20240303144147.rjdc3sbx7wdtghzj@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com> (raw)
In-Reply-To: <20240303141526.GA26420@lst.de>
On Sun, Mar 03, 2024 at 03:15:26PM +0100, Christoph Hellwig wrote:
> On Sun, Mar 03, 2024 at 09:10:48PM +0800, Zorro Lang wrote:
> > > # Convert free space (agno, block, length) to (start sector, end sector)
> > > _umount $loop_mnt
> > ^^^^^^^
> > Above line causes a conflict, due to it doesn't match the current shared/298 code. It's
> > "$UMOUNT_PROG $loop_mnt" in current fstests. So you might have another patch to do this
> > change.
>
> That line actually is from a patch in Darrick's patch queue that I'm
> working ontop of right now for some feture development. Sorry for not
> remembering to rebase against current for-next first.
Never mind:) As that "_umount $loop_mnt" isn't needed, I'll change the
single line only. This patch and the other patch "[PATCH] common:
dm-error now supports zoned devices" are in fstests' "patches-in-queue"
branch, they'll be in next release.
Thanks,
Zorro
>
>
prev parent reply other threads:[~2024-03-03 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 15:28 [PATCH] shared/298: run xfs_db against the loop device instead of the image file Christoph Hellwig
2024-03-01 17:47 ` Darrick J. Wong
2024-03-02 14:01 ` Christoph Hellwig
2024-03-02 19:51 ` Darrick J. Wong
2024-03-03 13:10 ` Zorro Lang
2024-03-03 14:15 ` Christoph Hellwig
2024-03-03 14:41 ` Zorro Lang [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=20240303144147.rjdc3sbx7wdtghzj@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com \
--to=zlang@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-xfs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).