From: "Darrick J. Wong" <djwong@kernel.org>
To: Ritesh Harjani <ritesh.list@gmail.com>
Cc: Catherine Hoang <catherine.hoang@oracle.com>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH v5] generic: add a test for atomic writes
Date: Thu, 17 Apr 2025 13:32:46 -0700 [thread overview]
Message-ID: <20250417203246.GD25667@frogsfrogsfrogs> (raw)
In-Reply-To: <20250415184404.GC25667@frogsfrogsfrogs>
On Tue, Apr 15, 2025 at 11:44:04AM -0700, Darrick J. Wong wrote:
<snip>
> > > +test_atomic_writes()
> > > +{
> > > + local bsize=$1
> > > +
> > > + get_mkfs_opts $bsize
> > > + _scratch_mkfs $mkfs_opts >> $seqres.full
> > > + _scratch_mount
> > > +
> > > + test "$FSTYP" = "xfs" && _xfs_force_bdev data $SCRATCH_MNT
> >
> > Ok, this (_xfs_force_bdev()) clears the rtinherit flag on $SCRATCH_MNT
> > in case if someone is passing that in MKFS_OPTIONS right? But since we
> > are using our own mkfs_opts, then do we still need this?
Yes, we still need this because _scratch_mkfs will try to combine
$MKFS_OPTIONS and the local $mkfs_opts, so rtinherit=1 could still be
set.
--D
> >
> > > +
> > > + testfile=$SCRATCH_MNT/testfile
> > > + touch $testfile
> > > +
> > > + file_min_write=$(_get_atomic_write_unit_min $testfile)
> > > + file_max_write=$(_get_atomic_write_unit_max $testfile)
> > > + file_max_segments=$(_get_atomic_write_segments_max $testfile)
> > > +
> > > + # Check that atomic min/max = FS block size
> > > + test $file_min_write -eq $bsize || \
> > > + echo "atomic write min $file_min_write, should be fs block size $bsize"
> > > + test $file_min_write -eq $bsize || \
> >
> > we should check for $file_max_write here ^^
> >
> > > + echo "atomic write max $file_max_write, should be fs block size $bsize"
> > > + test $file_max_segments -eq 1 || \
> > > + echo "atomic write max segments $file_max_segments, should be 1"
> > > +
> > > + # Check that we can perform an atomic write of len = FS block size
> > > + bytes_written=$($XFS_IO_PROG -dc "pwrite -A -D -V1 -b $bsize 0 $bsize" $testfile | \
> > > + grep wrote | awk -F'[/ ]' '{print $2}')
> > > + test $bytes_written -eq $bsize || echo "atomic write len=$bsize failed"
> > > +
> > > + # Check that we can perform an atomic single-block cow write
> > > + if [ "$FSTYP" == "xfs" ]; then
> > > + testfile_cp=$SCRATCH_MNT/testfile_copy
> > > + if _xfs_has_feature $SCRATCH_MNT reflink; then
> > > + cp --reflink $testfile $testfile_cp
> > > + fi
> > > + bytes_written=$($XFS_IO_PROG -dc "pwrite -A -D -V1 -b $bsize 0 $bsize" $testfile_cp | \
> > > + grep wrote | awk -F'[/ ]' '{print $2}')
> > > + test $bytes_written -eq $bsize || echo "atomic write on reflinked file failed"
> > > + fi
> > > +
> > > + # Check that we can perform an atomic write on an unwritten block
> > > + $XFS_IO_PROG -c "falloc $bsize $bsize" $testfile
> > > + bytes_written=$($XFS_IO_PROG -dc "pwrite -A -D -V1 -b $bsize $bsize $bsize" $testfile | \
> > > + grep wrote | awk -F'[/ ]' '{print $2}')
> > > + test $bytes_written -eq $bsize || echo "atomic write to unwritten block failed"
> > > +
> > > + # Check that we can perform an atomic write on a sparse hole
> > > + $XFS_IO_PROG -c "fpunch 0 $bsize" $testfile
> > > + bytes_written=$($XFS_IO_PROG -dc "pwrite -A -D -V1 -b $bsize 0 $bsize" $testfile | \
> > > + grep wrote | awk -F'[/ ]' '{print $2}')
> > > + test $bytes_written -eq $bsize || echo "atomic write to sparse hole failed"
> > > +
> > > + # Check that we can perform an atomic write on a fully mapped block
> > > + bytes_written=$($XFS_IO_PROG -dc "pwrite -A -D -V1 -b $bsize 0 $bsize" $testfile | \
> > > + grep wrote | awk -F'[/ ]' '{print $2}')
> > > + test $bytes_written -eq $bsize || echo "atomic write to mapped block failed"
> > > +
> > > + # Reject atomic write if len is out of bounds
> > > + $XFS_IO_PROG -dc "pwrite -A -D -V1 -b $bsize 0 $((bsize - 1))" $testfile 2>> $seqres.full && \
> > > + echo "atomic write len=$((bsize - 1)) should fail"
> > > + $XFS_IO_PROG -dc "pwrite -A -D -V1 -b $bsize 0 $((bsize + 1))" $testfile 2>> $seqres.full && \
> > > + echo "atomic write len=$((bsize + 1)) should fail"
> > > +
> > > + # Reject atomic write when iovecs > 1
> > > + $XFS_IO_PROG -dc "pwrite -A -D -V2 -b $bsize 0 $bsize" $testfile 2>> $seqres.full && \
> > > + echo "atomic write only supports iovec count of 1"
> > > +
> > > + # Reject atomic write when not using direct I/O
> > > + $XFS_IO_PROG -c "pwrite -A -V1 -b $bsize 0 $bsize" $testfile 2>> $seqres.full && \
> > > + echo "atomic write requires direct I/O"
> > > +
> > > + # Reject atomic write when offset % bsize != 0
> > > + $XFS_IO_PROG -dc "pwrite -A -D -V1 -b $bsize 1 $bsize" $testfile 2>> $seqres.full && \
> > > + echo "atomic write requires offset to be aligned to bsize"
> > > +
> > > + _scratch_unmount
> > > +}
> > > +
> > > +test_atomic_write_bounds()
> > > +{
> > > + local bsize=$1
> > > +
> > > + get_mkfs_opts $bsize
> > > + _scratch_mkfs $mkfs_opts >> $seqres.full
> > > + _scratch_mount
> > > +
> > > + test "$FSTYP" = "xfs" && _xfs_force_bdev data $SCRATCH_MNT
> >
> > ditto
> >
> > -ritesh
> >
> > > +
> > > + testfile=$SCRATCH_MNT/testfile
> > > + touch $testfile
> > > +
> > > + $XFS_IO_PROG -dc "pwrite -A -D -V1 -b $bsize 0 $bsize" $testfile 2>> $seqres.full && \
> > > + echo "atomic write should fail when bsize is out of bounds"
> > > +
> > > + _scratch_unmount
> > > +}
> > > +
> > > +sys_min_write=$(cat "/sys/block/$(_short_dev $SCRATCH_DEV)/queue/atomic_write_unit_min_bytes")
> > > +sys_max_write=$(cat "/sys/block/$(_short_dev $SCRATCH_DEV)/queue/atomic_write_unit_max_bytes")
> > > +
> > > +bdev_min_write=$(_get_atomic_write_unit_min $SCRATCH_DEV)
> > > +bdev_max_write=$(_get_atomic_write_unit_max $SCRATCH_DEV)
> > > +
> > > +# Test that statx atomic values are the same as sysfs values
> > > +if [ "$sys_min_write" -ne "$bdev_min_write" ]; then
> > > + echo "bdev min write != sys min write"
> > > +fi
> > > +if [ "$sys_max_write" -ne "$bdev_max_write" ]; then
> > > + echo "bdev max write != sys max write"
> > > +fi
> > > +
> > > +get_supported_bsize
> > > +
> > > +# Test all supported block sizes between bdev min and max
> > > +for ((bsize=$bdev_min_write; bsize<=bdev_max_write; bsize*=2)); do
> > > + if [ "$bsize" -ge "$min_bsize" ] && [ "$bsize" -le "$max_bsize" ]; then
> > > + test_atomic_writes $bsize
> > > + fi
> > > +done;
> > > +
> > > +# Check that atomic write fails if bsize < bdev min or bsize > bdev max
> > > +if [ $((bdev_min_write / 2)) -ge "$min_bsize" ]; then
> > > + test_atomic_write_bounds $((bdev_min_write / 2))
> > > +fi
> > > +if [ $((bdev_max_write * 2)) -le "$max_bsize" ]; then
> > > + test_atomic_write_bounds $((bdev_max_write * 2))
> > > +fi
> > > +
> > > +# success, all done
> > > +echo Silence is golden
> > > +status=0
> > > +exit
> > > diff --git a/tests/generic/765.out b/tests/generic/765.out
> > > new file mode 100644
> > > index 00000000..39c254ae
> > > --- /dev/null
> > > +++ b/tests/generic/765.out
> > > @@ -0,0 +1,2 @@
> > > +QA output created by 765
> > > +Silence is golden
> > > --
> > > 2.34.1
> >
>
next prev parent reply other threads:[~2025-04-17 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 4:23 [PATCH v5] generic: add a test for atomic writes Catherine Hoang
2025-04-15 12:59 ` Ritesh Harjani
2025-04-15 18:44 ` Darrick J. Wong
2025-04-17 20:32 ` Darrick J. Wong [this message]
2025-05-02 7:12 ` Christoph Hellwig
2025-05-02 19:39 ` Darrick J. Wong
2025-05-05 5:37 ` Christoph Hellwig
2025-05-05 14:57 ` 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=20250417203246.GD25667@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=catherine.hoang@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ritesh.list@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.