From: hch <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Hans Holmberg <Hans.Holmberg@wdc.com>,
"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>,
"david@fromorbit.com" <david@fromorbit.com>, hch <hch@lst.de>
Subject: Re: [PATCH 1/2] xfs: add mount test for read only rt devices
Date: Wed, 30 Apr 2025 14:56:18 +0200 [thread overview]
Message-ID: <20250430125618.GA834@lst.de> (raw)
In-Reply-To: <20250429145220.GU25675@frogsfrogsfrogs>
On Tue, Apr 29, 2025 at 07:52:21AM -0700, Darrick J. Wong wrote:
> And come to think of it, weren't there supposed to be pmem filesystems
> which would run entirely off a pmem character device and not have a
> block interface available at all?
That support never materialized, and if it at some does it will need a
few changes all over xfstets, so no need to worry now.
next prev parent reply other threads:[~2025-04-30 12:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 9:03 [PATCH 0/2] add read-only logdev/rtdev mount-remount tests Hans Holmberg
2025-04-25 9:03 ` [PATCH 1/2] xfs: add mount test for read only rt devices Hans Holmberg
2025-04-25 15:03 ` Darrick J. Wong
2025-04-29 12:03 ` Hans Holmberg
2025-04-29 14:52 ` Darrick J. Wong
2025-04-30 12:56 ` hch [this message]
2025-04-30 14:49 ` Darrick J. Wong
2025-05-07 8:57 ` Hans Holmberg
2025-05-07 10:23 ` Hans Holmberg
2025-04-25 9:03 ` [PATCH 2/2] xfs: add mount test for read only log devices Hans Holmberg
2025-04-25 15:05 ` Darrick J. Wong
2025-04-28 12:16 ` Hans Holmberg
2025-04-28 15:58 ` Darrick J. Wong
2025-04-30 8:26 ` Hans Holmberg
2025-04-30 14:52 ` Darrick J. Wong
2025-05-02 11:40 ` Hans Holmberg
-- strict thread matches above, loose matches on Subject: below --
2025-06-09 11:03 [PATCH 0/2] Add xfs test coverage for ro external dev mounts Hans Holmberg
2025-06-09 11:03 ` [PATCH 1/2] xfs: add mount test for read only rt devices Hans Holmberg
2025-06-09 16:18 ` Darrick J. Wong
2025-06-10 3:36 ` hch
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=20250430125618.GA834@lst.de \
--to=hch@lst.de \
--cc=Hans.Holmberg@wdc.com \
--cc=cem@kernel.org \
--cc=david@fromorbit.com \
--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;
as well as URLs for NNTP newsgroup(s).