All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] fsx: disable allocsp_calls if -F is specified
Date: Sat, 29 Jan 2022 20:56:44 -0800	[thread overview]
Message-ID: <20220130045644.GP13563@magnolia> (raw)
In-Reply-To: <20220129044431.1404283-1-zlang@redhat.com>

On Sat, Jan 29, 2022 at 12:44:31PM +0800, Zorro Lang wrote:
> As the fsx.c source code says:
>   int     fallocate_calls = 1;            /* -F flag disables */
>   int     allocsp_calls = 1;              /* -F flag disables */
> 
> The allocsp_calls and fallocate_calls should be disabled, if the -F
> option is specified. But current fsx forgets to disable allocsp_calls
> as is documented.
> 
> Signed-off-by: Zorro Lang <zlang@redhat.com>
> ---
> 
> Hi Darrick,
> 
> Please help to take a look. I'm not sure if you'd like to disable
> allocsp_calls by -F flag, or just copied that line then forgot to
> change the F to another ?

Nah, that's ... fine.  Thanks for fixing this.  I hate ALLOCSP. :)
Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D


> Thanks,
> Zorro
> 
>  ltp/fsx.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/ltp/fsx.c b/ltp/fsx.c
> index 520e53a2..3ee37fe8 100644
> --- a/ltp/fsx.c
> +++ b/ltp/fsx.c
> @@ -2835,6 +2835,7 @@ main(int argc, char **argv)
>  			break;
>  		case 'F':
>  			fallocate_calls = 0;
> +			allocsp_calls = 0;
>  			break;
>  		case 'K':
>  			keep_size_calls = 0;
> -- 
> 2.31.1
> 

      reply	other threads:[~2022-01-30  4:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29  4:44 [PATCH] fsx: disable allocsp_calls if -F is specified Zorro Lang
2022-01-30  4:56 ` 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=20220130045644.GP13563@magnolia \
    --to=djwong@kernel.org \
    --cc=fstests@vger.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 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.