From: Brian Foster <bfoster@redhat.com>
To: fdmanana@kernel.org
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH 2/4] fsx: fix infinite/too long loops when generating ranges for clone operations
Date: Fri, 17 Apr 2020 13:10:28 -0400 [thread overview]
Message-ID: <20200417171028.GC13463@bfoster> (raw)
In-Reply-To: <20200408103604.11395-1-fdmanana@kernel.org>
On Wed, Apr 08, 2020 at 11:36:04AM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> While running generic/457 I've had fsx taking a lot of CPU time and not
> making any progress for over an hour. Attaching gdb to the fsx process
> revealed that fsx was in the loop that generates the ranges for a clone
> operation, in particular the loop seemed to never end because the range
> defined by 'offset2' kept overlapping with the range defined by 'offset'.
> So far this happened two times in one of my test VMs with generic/457.
>
> Fix this by breaking out of the loop after trying 30 times, like we
> currently do for dedupe operations, which results in logging the operation
> as skipped.
>
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
> ---
Reviewed-by: Brian Foster <bfoster@redhat.com>
> ltp/fsx.c | 28 ++++++++++++++++++----------
> 1 file changed, 18 insertions(+), 10 deletions(-)
>
> diff --git a/ltp/fsx.c b/ltp/fsx.c
> index fa383c94..5949ebf0 100644
> --- a/ltp/fsx.c
> +++ b/ltp/fsx.c
> @@ -2004,16 +2004,24 @@ test(void)
> keep_size = random() % 2;
> break;
> case OP_CLONE_RANGE:
> - TRIM_OFF_LEN(offset, size, file_size);
> - offset = offset & ~(block_size - 1);
> - size = size & ~(block_size - 1);
> - do {
> - offset2 = random();
> - TRIM_OFF(offset2, maxfilelen);
> - offset2 = offset2 & ~(block_size - 1);
> - } while (range_overlaps(offset, offset2, size) ||
> - offset2 + size > maxfilelen);
> - break;
> + {
> + int tries = 0;
> +
> + TRIM_OFF_LEN(offset, size, file_size);
> + offset = offset & ~(block_size - 1);
> + size = size & ~(block_size - 1);
> + do {
> + if (tries++ >= 30) {
> + size = 0;
> + break;
> + }
> + offset2 = random();
> + TRIM_OFF(offset2, maxfilelen);
> + offset2 = offset2 & ~(block_size - 1);
> + } while (range_overlaps(offset, offset2, size) ||
> + offset2 + size > maxfilelen);
> + break;
> + }
> case OP_DEDUPE_RANGE:
> {
> int tries = 0;
> --
> 2.11.0
>
next prev parent reply other threads:[~2020-04-17 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 10:36 [PATCH 2/4] fsx: fix infinite/too long loops when generating ranges for clone operations fdmanana
2020-04-17 17:10 ` Brian Foster [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-20 17:09 fdmanana
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=20200417171028.GC13463@bfoster \
--to=bfoster@redhat.com \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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 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.