From: Andrea Parri <parri.andrea@gmail.com>
To: Zorro Lang <zlang@kernel.org>
Cc: fstests@vger.kernel.org, "Darrick J . Wong" <djwong@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
linux-xfs@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2] xfs: exercise a failed CoW conversion during writeback
Date: Mon, 28 Sep 2026 16:15:35 +0200 [thread overview]
Message-ID: <20260928141541.305360-1-parri.andrea@gmail.com> (raw)
In-Reply-To: <arprh9oyZEXs25CQ@zlang-mailbox>
On Mon, Sep 28, 2026 at 09:53:29PM +0800, Zorro Lang wrote:
> > +seq=0
>
> In fstests, $seq is a core global variable representing the test sequence
> number. Overwriting it here might lead to unexpected side effects with
> framework helpers or cleanup logic. Could we rename this loop variable to
> something else to avoid trouble? If you need, I can help that when I merge
> it.
Good catch, thanks. Yes, please fold it in when you merge, if that's
fine with you; the rename I had in mind is just:
@@ -48,11 +48,11 @@ _cp_reflink $SCRATCH_MNT/file1 $SCRATCH_MNT/file2
# Dirty several widely separated ranges of file2's CoW extents so that a
# single writepages() call has to submit more than one ioend.
-seq=0
-while [ $seq -lt $nr ]; do
- off=$((seq * blksz * 2))
+i=0
+while [ $i -lt $nr ]; do
+ off=$((i * blksz * 2))
_pwrite_byte 0x59 $off $blksz $SCRATCH_MNT/file2 >> $seqres.full
- seq=$((seq + 1))
+ i=$((i + 1))
done
echo "Inject wb_cow_convert_error"
I'm happy to send a v3 instead if you'd prefer.
Thanks!
Andrea
next prev parent reply other threads:[~2026-09-28 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 8:50 [PATCH v2] xfs: exercise a failed CoW conversion during writeback Andrea Parri
2026-09-28 13:53 ` Zorro Lang
2026-09-28 14:15 ` Andrea Parri [this message]
2026-09-28 15:41 ` Darrick J. Wong
2026-09-28 16:24 ` Andrea Parri
2026-09-28 21:47 ` Zorro Lang
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=20260928141541.305360-1-parri.andrea@gmail.com \
--to=parri.andrea@gmail.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@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 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.