From: "Darrick J. Wong" <djwong@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Zorro Lang <zlang@redhat.com>,
Chandan Babu R <chandan.babu@oracle.com>,
Luis Chamberlain <mcgrof@kernel.org>,
fstests@vger.kernel.org
Subject: Re: [PATCH] generic/{175,297,298}: fix use of uninitialized var
Date: Mon, 14 Aug 2023 19:16:59 -0700 [thread overview]
Message-ID: <20230815021659.GS11377@frogsfrogsfrogs> (raw)
In-Reply-To: <CAOQ4uxiwyCvEshtc9QDUKKXyO0U77cq+ENy7FAz+9v4s7YUoSQ@mail.gmail.com>
On Sun, Aug 13, 2023 at 09:53:30PM +0300, Amir Goldstein wrote:
> On Sun, Aug 13, 2023 at 6:35 PM Darrick J. Wong <djwong@kernel.org> wrote:
> >
> > On Sat, Aug 12, 2023 at 06:15:00PM +0300, Amir Goldstein wrote:
> > > Not sure how those tests pass in regression tests.
> > > Probably truncate silently fails and is not critical to the test.
> > >
> > > in kdevops I get errors like:
> > > /data/fstests-install/xfstests/tests/generic/298: line 45: /dev/loop12):
> > > syntax error: operand expected (error token is "/dev/loop12)")
> > >
> > > Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> > > ---
> > > tests/generic/175 | 2 +-
> > > tests/generic/297 | 2 +-
> > > tests/generic/298 | 2 +-
> > > 3 files changed, 3 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/tests/generic/175 b/tests/generic/175
> > > index 07af2199..14825a39 100755
> > > --- a/tests/generic/175
> > > +++ b/tests/generic/175
> > > @@ -33,7 +33,7 @@ _pwrite_byte 0x61 0 $blksz "$testdir/file1" >> "$seqres.full"
> > >
> > > fnr=19
> > > echo "Create extents"
> > > -truncate -s $(( (2 ** i) * blksz)) "$testdir/file1"
> > > +truncate -s $(( (2 ** (fnr + 1)) * blksz)) "$testdir/file1"
> > > for i in $(seq 0 $fnr); do
> >
> > Hmm. Frankly I don't remember why I put those truncate calls in there.
>
> You specifically added truncate in commit
> ddf6ff2f reflink: ensure that we can handle reflinking a lot of extents
> and then it was copied to the two new tests.
> maybe this will give you a hint?
Alas, no. Total etch-a-sketch over here. :(
AFAICT the tests work just fine without the truncate calls, so let's
remove them.
--D
> > Does the test still work if you remove them entirely? AFAICT the test
> > writes a single block's worth of data to the file, then truncates the
> > file size to one block. Which I think is pointless.
> >
> > > echo " ++ Reflink size $i, $((2 ** i)) blocks" >> "$seqres.full"
> > > n=$(( (2 ** i) * blksz))
> > > diff --git a/tests/generic/297 b/tests/generic/297
> > > index 6bdc3e1c..1fc48671 100755
> > > --- a/tests/generic/297
> > > +++ b/tests/generic/297
> > > @@ -42,7 +42,7 @@ _pwrite_byte 0x61 0 $blksz $testdir/file1 >> $seqres.full
> > > fnr=26 # 2^26 reflink extents should be enough to find a slow op?
> > > timeout=8 # guarantee a good long run...
> > > echo "Find a reflink size that takes a long time"
> > > -truncate -s $(( (2 ** i) * blksz)) $testdir/file1
> > > +truncate -s $(( (2 ** (fnr + 1)) * blksz)) $testdir/file1
> > > for i in $(seq 0 $fnr); do
> > > echo " ++ Reflink size $i, $((2 ** i)) blocks" >> $seqres.full
> > > n=$(( (2 ** i) * blksz))
> >
> > The loop control logic could be converted to:
> >
> > echo "Find a reflink size that takes a long time"
> > deadline="$(( $(date +%s) + timeout ))"
> > for ((i = 0, now = $(date +%s); i < fnr && now < deadline; i++, now = $(date +%s))); do
> > echo " ++ Reflink size $i, $((2 ** i)) blocks" >> $seqres.full
> > n=$(( (2 ** i) * blksz))
> > $XFS_IO_PROG -f -c "reflink $testdir/file1 0 $n $n" $testdir/file1 >> $seqres.full 2>&1
> > done
> >
> > (also in 298)
> >
>
> Whatever works is fine by me.
> Feel free to keep my commit message or drop it.
>
> Thanks,
> Amir.
prev parent reply other threads:[~2023-08-15 2:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 15:15 [PATCH] generic/{175,297,298}: fix use of uninitialized var Amir Goldstein
2023-08-13 14:52 ` Zorro Lang
2023-08-13 15:35 ` Darrick J. Wong
2023-08-13 18:53 ` Amir Goldstein
2023-08-15 2:16 ` Darrick J. Wong [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=20230815021659.GS11377@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=mcgrof@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