From: Zorro Lang <zlang@redhat.com>
To: Brian Foster <bfoster@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v2] generic/563: use a loop device to avoid partition incompatibility
Date: Tue, 15 Dec 2020 08:13:49 +0800 [thread overview]
Message-ID: <20201215001349.GB14354@localhost.localdomain> (raw)
In-Reply-To: <20201214171854.2260900-1-bfoster@redhat.com>
On Mon, Dec 14, 2020 at 12:18:54PM -0500, Brian Foster wrote:
> cgroup writeback accounting does not track partition level
> statistics. Instead, I/O is accounted against the parent device. As
> a result, the test fails if the scratch device happens to be a
> device partition. Since parent level stats are potentially polluted
> by factors external to the test, wrap the scratch device in a
> loopback device to guarantee the test always runs on a top-level
> block device.
>
> Reported-by: Boyang Xue <bxue@redhat.com>
> Signed-off-by: Brian Foster <bfoster@redhat.com>
> ---
>
> v2:
> - Use _require_scratch_nocheck() since the scratch device is not used
> directly.
V2 looks good to me, thanks Brian.
Reviewed-by: Zorro Lang <zlang@redhat.com>
> v1: https://lore.kernel.org/fstests/20201210161426.1927144-1-bfoster@redhat.com/
>
> tests/generic/563 | 23 +++++++++++++++--------
> 1 file changed, 15 insertions(+), 8 deletions(-)
>
> diff --git a/tests/generic/563 b/tests/generic/563
> index 51deaa2f..b113eacf 100755
> --- a/tests/generic/563
> +++ b/tests/generic/563
> @@ -2,7 +2,7 @@
> # SPDX-License-Identifier: GPL-2.0
> # Copyright (c) 2019 Red Hat, Inc. All Rights Reserved.
> #
> -# FS QA Test No. 011
> +# FS QA Test No. 563
> #
> # This test verifies that cgroup aware writeback properly accounts I/Os in
> # various scenarios. We perform reads/writes from different combinations of
> @@ -26,6 +26,8 @@ _cleanup()
>
> echo $$ > $cgdir/cgroup.procs
> rmdir $cgdir/$seq-cg* > /dev/null 2>&1
> + umount $SCRATCH_MNT > /dev/null 2>&1
> + _destroy_loop_device $LOOP_DEV > /dev/null 2>&1
> }
>
> # get standard environment, filters and checks
> @@ -40,16 +42,14 @@ rm -f $seqres.full
>
> # Modify as appropriate.
> _supported_fs generic
> -_require_scratch
> +_require_scratch_nocheck
> _require_cgroup2 io
> +_require_loop
>
> # cgroup v2 writeback is only support on block devices so far
> _require_block_device $SCRATCH_DEV
>
> -smajor=$((0x`stat -L -c %t $SCRATCH_DEV`))
> -sminor=$((0x`stat -L -c %T $SCRATCH_DEV`))
> cgdir=$CGROUP2_PATH
> -
> iosize=$((1024 * 1024 * 8))
>
> # Check cgroup read/write charges against expected values. Allow for some
> @@ -89,12 +89,19 @@ reset()
> rmdir $cgdir/$seq-cg* > /dev/null 2>&1
> $XFS_IO_PROG -fc "pwrite 0 $iosize" $SCRATCH_MNT/file \
> >> $seqres.full 2>&1
> - _scratch_cycle_mount || _fail "mount failed"
> + umount $SCRATCH_MNT || _fail "umount failed"
> + _mount $LOOP_DEV $SCRATCH_MNT || _fail "mount failed"
> stat $SCRATCH_MNT/file > /dev/null
> }
>
> -_scratch_mkfs >> $seqres.full 2>&1
> -_scratch_mount
> +# cgroup I/O accounting doesn't work on partitions. Use a loop device to rule
> +# that out.
> +LOOP_DEV=$(_create_loop_device $SCRATCH_DEV)
> +smajor=$((0x`stat -L -c %t $LOOP_DEV`))
> +sminor=$((0x`stat -L -c %T $LOOP_DEV`))
> +
> +_mkfs_dev $LOOP_DEV >> $seqres.full 2>&1
> +_mount $LOOP_DEV $SCRATCH_MNT || _fail "mount failed"
>
> echo "+io" > $cgdir/cgroup.subtree_control || _fail "subtree control"
>
> --
> 2.26.2
>
prev parent reply other threads:[~2020-12-15 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 17:18 [PATCH v2] generic/563: use a loop device to avoid partition incompatibility Brian Foster
2020-12-15 0:13 ` Zorro Lang [this message]
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=20201215001349.GB14354@localhost.localdomain \
--to=zlang@redhat.com \
--cc=bfoster@redhat.com \
--cc=fstests@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