From: Disha Goel <disgoel@linux.ibm.com>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>,
Zorro Lang <zlang@redhat.com>,
fstests@vger.kernel.org
Cc: djwong@kernel.org, fdmanana@suse.com, ritesh.list@gmail.com,
naohiro.aota@wdc.com, wqu@suse.com
Subject: Re: [PATCH 5/6] generic/775: Fix an infinite loop due to variable name clash
Date: Tue, 14 Apr 2026 15:35:26 +0530 [thread overview]
Message-ID: <3f9045a6-0e62-4df1-81c9-7378cb0587dc@linux.ibm.com> (raw)
In-Reply-To: <9c8783dc648ef861f81cba8d5d692932b795e262.1775802601.git.ojaswin@linux.ibm.com>
On 10/04/26 12:06 pm, Ojaswin Mujoo wrote:
> We use i as the iteration variable in the main test loop as well as some
> internal loops. Due to this clash, $i variable of main test loops was
> getting modified by the following loop in prep_mixed_mapping().
>
> for ((i=0; i<num_blocks; i++)); do
>
> If num_blocks is less than 10 (example ext4 with blocksize 4k and
> cluster size 8k) i would always be set as 3 and the main loop would
> never exit. Use local variable to fix this and while we are at it,
> rename it for clarity.
>
> Reported-by: Disha Goel <disgoel@linux.ibm.com>
> Signed-off-by: Ojaswin Mujoo <ojaswin@linux.ibm.com>
I've tested this patch and it fixes the infinite loop issue. The test
now runs to completion without getting stuck in an infinite loop.
Tested-by: Disha Goel <disgoel@linux.ibm.com>
> ---
> tests/generic/775 | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tests/generic/775 b/tests/generic/775
> index 2a4287bb..6dc005a0 100755
> --- a/tests/generic/775
> +++ b/tests/generic/775
> @@ -41,7 +41,8 @@ prep_mixed_mapping() {
>
> local operations=("W" "H" "U")
> local num_blocks=$((awu_max / blksz))
> - for ((i=0; i<num_blocks; i++)); do
> + local blkno
> + for ((blkno=0; blkno<num_blocks; blkno++)); do
> local index=$((RANDOM % ${#operations[@]}))
> local map="${operations[$index]}"
> local mapping="${mapping}${map}"
--
Regards,
Disha
next prev parent reply other threads:[~2026-04-14 10:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 6:36 [PATCH v2 0/6] Atomic write test fixes & refactoring Ojaswin Mujoo
2026-04-10 6:36 ` [PATCH 1/6] ext4/061,062: Minor fixes and refactoring Ojaswin Mujoo
2026-04-14 9:52 ` Disha Goel
2026-04-10 6:36 ` [PATCH 2/6] common/rc: Add _sysfs_queue_path helper with partition support Ojaswin Mujoo
2026-04-10 16:50 ` Darrick J. Wong
2026-04-10 6:36 ` [PATCH 3/6] generic/765: Fix sysfs queue path for nvme partitions Ojaswin Mujoo
2026-04-10 16:50 ` Darrick J. Wong
2026-04-14 9:58 ` Disha Goel
2026-04-10 6:36 ` [PATCH 4/6] generic/765: Ignore mkfs warning Ojaswin Mujoo
2026-04-10 16:54 ` Darrick J. Wong
2026-04-12 17:08 ` Ojaswin Mujoo
2026-04-13 9:04 ` Ojaswin Mujoo
2026-04-13 16:21 ` Darrick J. Wong
2026-04-13 20:42 ` Theodore Tso
2026-04-13 23:28 ` Darrick J. Wong
2026-04-15 18:52 ` Ojaswin Mujoo
2026-04-16 15:55 ` Zorro Lang
2026-04-12 19:23 ` Zorro Lang
2026-04-13 9:09 ` Ojaswin Mujoo
2026-04-14 10:02 ` Disha Goel
2026-04-10 6:36 ` [PATCH 5/6] generic/775: Fix an infinite loop due to variable name clash Ojaswin Mujoo
2026-04-10 16:51 ` Darrick J. Wong
2026-04-14 10:05 ` Disha Goel [this message]
2026-04-10 6:36 ` [PATCH 6/6] treewide: Use _sysfs_queue_path helper in all queue access locations Ojaswin Mujoo
2026-04-10 16:52 ` 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=3f9045a6-0e62-4df1-81c9-7378cb0587dc@linux.ibm.com \
--to=disgoel@linux.ibm.com \
--cc=djwong@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=wqu@suse.com \
--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