From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: hch <hch@lst.de>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Subject: Re: [bug report] xfs/802 failure due to mssing fstype report by lsblk
Date: Mon, 9 Feb 2026 07:54:38 +0000 [thread overview]
Message-ID: <aYmRhwnL286jv550@shinmob> (raw)
In-Reply-To: <20260209062821.GA9021@lst.de>
On Feb 09, 2026 / 07:28, hch wrote:
> On Sun, Feb 08, 2026 at 10:07:16PM -0800, Darrick J. Wong wrote:
> > Waitaminute, how can you even format xfs on nullblk to run fstests?
> > Isn't that the bdev that silently discards everything written to it, and
> > returns zero on reads??
>
> nullblk can be used with or without a backing store. In the former
> case it will not always return zeroes on reads obviously.
Yes, null_blk has the "memory_backed" parameter. When 1 is set to this, data
written to the null_blk device is kept and read back. I create two 8GiB null_blk
devices enabling this memory_backed option, and use them as TEST_DEV and
SCRATCH_DEV for the regular xfs test runs.
next prev parent reply other threads:[~2026-02-09 7:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 8:40 [bug report] xfs/802 failure due to mssing fstype report by lsblk Shinichiro Kawasaki
2026-02-06 17:38 ` Darrick J. Wong
2026-02-09 2:50 ` Shinichiro Kawasaki
2026-02-09 6:07 ` Darrick J. Wong
2026-02-09 6:28 ` hch
2026-02-09 7:54 ` Shinichiro Kawasaki [this message]
2026-02-10 2:00 ` Darrick J. Wong
2026-02-10 6:17 ` Darrick J. Wong
2026-02-10 6:19 ` Shinichiro Kawasaki
2026-02-13 22:14 ` Darrick J. Wong
2026-02-14 6:39 ` Shinichiro Kawasaki
2026-02-14 7:39 ` Darrick J. Wong
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=aYmRhwnL286jv550@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=djwong@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