From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
zlang@kernel.org, fstests@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: test libxfs handling of missing RT devices
Date: Tue, 15 Sep 2026 08:22:47 +0200 [thread overview]
Message-ID: <20260915062247.GA13095@lst.de> (raw)
In-Reply-To: <20260914150549.GO6265@frogsfrogsfrogs>
On Mon, Sep 14, 2026 at 08:05:49AM -0700, Darrick J. Wong wrote:
> > + _unmount $LOOP_MNT 2>/dev/null
> > + [ -n "$loop_dev" ] && _destroy_loop_device $loop_dev
> > + rm -rf $LOOP_IMG $LOOP_MNT
>
> I don't see any users of loop devices here?
Yeah. I initially started writing it loop based but got fed up with
that and decided that we can just require an rt dev run for test
coverage..
next prev parent reply other threads:[~2026-09-15 6:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 11:36 [PATCH] xfs: test libxfs handling of missing RT devices Christoph Hellwig
2026-09-14 15:05 ` Darrick J. Wong
2026-09-15 6:22 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-25 5:15 Christoph Hellwig
2026-09-25 19:47 ` Darrick J. Wong
2026-09-27 12:20 ` Zorro Lang
2026-09-28 5:35 ` Christoph Hellwig
2026-09-28 6:58 ` Christoph Hellwig
2026-09-28 9:56 ` Zorro Lang
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=20260915062247.GA13095@lst.de \
--to=hch@lst.de \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--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