From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: zlang@redhat.com, fstests@vger.kernel.org, guan@eryu.me,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 10/10] swapext: make sure that we don't swap unwritten extents unless they're part of a rt extent(??)
Date: Wed, 19 Jun 2024 09:58:45 -0700 [thread overview]
Message-ID: <20240619165845.GO103034@frogsfrogsfrogs> (raw)
In-Reply-To: <ZnJ2jieRl4-B70Ux@infradead.org>
On Tue, Jun 18, 2024 at 11:11:26PM -0700, Christoph Hellwig wrote:
> On Mon, Jun 17, 2024 at 05:49:21PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> >
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
>
> Can you add a commit message explaining what this test does and why
> you wrote it?
Whoops, another one escaped:
exchangerange: make sure that we don't swap unwritten extents unless they're part of a rt extent
By default, the FILE1_WRITTEN flag for the EXCHANGERANGE ioctl isn't
supposed to touch anything except for written extents. In other words,
it shouldn't exchange delalloc reservations, unwritten preallocations,
or holes. The XFS implementation flushes dirty pagecache to disk so
there should never be delalloc reservations running through the
exchangerange machinery, but there can be unwritten extents.
Hence, write a test to make sure that unwritten extents don't get moved
around. This test opts itself out for realtime filesystems where the
allocation unit is larger than 1 fsblock because xfs has to move full
allocation units, and that requires exchanging of partially written rt
extents.
--D
next prev parent reply other threads:[~2024-06-19 16:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 0:46 [PATCHSET v30.6 2/6] fstests: atomic file updates Darrick J. Wong
2024-06-18 0:47 ` [PATCH 01/10] misc: split swapext and exchangerange Darrick J. Wong
2024-06-19 6:06 ` Christoph Hellwig
2024-06-18 0:47 ` [PATCH 02/10] misc: change xfs_io -c swapext to exchangerange Darrick J. Wong
2024-06-19 6:07 ` Christoph Hellwig
2024-06-18 0:47 ` [PATCH 03/10] generic/710: repurpose this for exchangerange vs. quota testing Darrick J. Wong
2024-06-19 6:08 ` Christoph Hellwig
2024-06-19 17:23 ` Darrick J. Wong
2024-06-20 16:55 ` Darrick J. Wong
2024-06-20 19:06 ` Zorro Lang
2024-06-20 19:20 ` Darrick J. Wong
2024-06-18 0:47 ` [PATCH 04/10] generic/717: remove obsolete check Darrick J. Wong
2024-06-19 6:09 ` Christoph Hellwig
2024-06-19 16:31 ` Darrick J. Wong
2024-06-20 18:58 ` Zorro Lang
2024-06-18 0:48 ` [PATCH 05/10] ltp/{fsstress,fsx}: make the exchangerange naming consistent Darrick J. Wong
2024-06-19 6:09 ` Christoph Hellwig
2024-06-18 0:48 ` [PATCH 06/10] misc: flip HAVE_XFS_IOC_EXCHANGE_RANGE logic Darrick J. Wong
2024-06-19 6:09 ` Christoph Hellwig
2024-06-18 0:48 ` [PATCH 07/10] src/fiexchange.h: update XFS_IOC_EXCHANGE_RANGE definitions Darrick J. Wong
2024-06-19 6:10 ` Christoph Hellwig
2024-06-18 0:48 ` [PATCH 08/10] xfs/122: fix for exchrange conversion Darrick J. Wong
2024-06-19 6:10 ` Christoph Hellwig
2024-06-18 0:49 ` [PATCH 09/10] xfs/206: screen out exchange-range from golden output Darrick J. Wong
2024-06-19 6:10 ` Christoph Hellwig
2024-06-18 0:49 ` [PATCH 10/10] swapext: make sure that we don't swap unwritten extents unless they're part of a rt extent(??) Darrick J. Wong
2024-06-19 6:11 ` Christoph Hellwig
2024-06-19 16:58 ` Darrick J. Wong [this message]
2024-06-20 4:24 ` Christoph Hellwig
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=20240619165845.GO103034@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.com \
/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