linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 3/4] fsx: fix infinite/too long loops when generating ranges for copy_file_range
Date: Fri, 17 Apr 2020 13:10:37 -0400	[thread overview]
Message-ID: <20200417171037.GD13463@bfoster> (raw)
In-Reply-To: <20200408103616.11458-1-fdmanana@kernel.org>

On Wed, Apr 08, 2020 at 11:36:16AM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> While running generic/521 I've had fsx taking a lot of CPU time and not
> making any progress for several hours. Attaching gdb to the fsx process
> revealed that fsx was in the loop that generates the ranges for a
> copy_file_range 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 one time only in one of my test VMs with generic/521.
> 
> 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 | 30 +++++++++++++++++++-----------
>  1 file changed, 19 insertions(+), 11 deletions(-)
> 
> diff --git a/ltp/fsx.c b/ltp/fsx.c
> index 5949ebf0..89a5f60e 100644
> --- a/ltp/fsx.c
> +++ b/ltp/fsx.c
> @@ -2042,17 +2042,25 @@ test(void)
>  			break;
>  		}
>  	case OP_COPY_RANGE:
> -		TRIM_OFF_LEN(offset, size, file_size);
> -		offset -= offset % readbdy;
> -		if (o_direct)
> -			size -= size % readbdy;
> -		do {
> -			offset2 = random();
> -			TRIM_OFF(offset2, maxfilelen);
> -			offset2 -= offset2 % writebdy;
> -		} while (range_overlaps(offset, offset2, size) ||
> -			 offset2 + size > maxfilelen);
> -		break;
> +		{
> +			int tries = 0;
> +
> +			TRIM_OFF_LEN(offset, size, file_size);
> +			offset -= offset % readbdy;
> +			if (o_direct)
> +				size -= size % readbdy;
> +			do {
> +				if (tries++ >= 30) {
> +					size = 0;
> +					break;
> +				}
> +				offset2 = random();
> +				TRIM_OFF(offset2, maxfilelen);
> +				offset2 -= offset2 % writebdy;
> +			} while (range_overlaps(offset, offset2, size) ||
> +				 offset2 + size > maxfilelen);
> +			break;
> +		}
>  	}
>  
>  have_op:
> -- 
> 2.11.0
> 


  reply	other threads:[~2020-04-17 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08 10:36 [PATCH 3/4] fsx: fix infinite/too long loops when generating ranges for copy_file_range 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=20200417171037.GD13463@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).