linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Eric Sandeen <sandeen@sandeen.net>,
	linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] fsr: fix uninitialized fs usage after timeout
Date: Wed, 21 Jun 2017 17:49:59 -0400	[thread overview]
Message-ID: <07b82f1b-040f-b472-12f8-fa9eeaf9508f@suse.com> (raw)
In-Reply-To: <118e7672-680a-689d-6b74-7169a38b3d89@sandeen.net>


[-- Attachment #1.1: Type: text/plain, Size: 2444 bytes --]

On 6/21/17 3:28 PM, Eric Sandeen wrote:
> On 6/2/17 1:20 PM, Jeff Mahoney wrote:
>> In the main loop of fsrallfs, we exit when we've hit the timeout but
>> we increment fs before we get there.  If we're operating on the last
>> file system in the array, we'll hit an uninitialized fsdesc and
>> crash in fsrall_cleanup.
> 
> Ugh, really - nobody should be using the defrag-the-world mode,
> but we ship it, so ...
> 
>> Signed-off-by: Jeff Mahoney <jeffm@suse.com>
>> ---
>>  fsr/xfs_fsr.c | 4 +---
>>  1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/fsr/xfs_fsr.c b/fsr/xfs_fsr.c
>> index 517b75f0..e695c243 100644
>> --- a/fsr/xfs_fsr.c
>> +++ b/fsr/xfs_fsr.c
>> @@ -598,7 +598,7 @@ fsrallfs(char *mtab, int howlong, char *leftofffile)
>>  	signal(SIGTERM, aborter);
>>
>>  	/* reorg for 'howlong' -- checked in 'fsrfs' */
>> -	while (endtime > time(0)) {
>> +	for (; endtime > time(0); fs->npass++, fs++) {
>>  		pid_t pid;
>>  		if (fs == fsend)
>>  			fs = fsbase;
>> @@ -629,8 +629,6 @@ fsrallfs(char *mtab, int howlong, char *leftofffile)
>>  			break;
>>  		}
>>  		startino = 0;  /* reset after the first time through */
>> -		fs->npass++;
>> -		fs++;
>>  	}
>>  	fsrall_cleanup(endtime <= time(0));
>>  }
> 
> I hate to be that PITA maintainer who only wants to do it his way ;) but
> would this be any tidier?
> 
> I'm just not that big a fan of "for(; ....)" loops.

Sure, this'll work just as well.

-Jeff

> diff --git a/fsr/xfs_fsr.c b/fsr/xfs_fsr.c
> index 517b75f..3a5f683 100644
> --- a/fsr/xfs_fsr.c
> +++ b/fsr/xfs_fsr.c
> @@ -600,12 +600,6 @@ fsrallfs(char *mtab, int howlong, char *leftofffile)
>  	/* reorg for 'howlong' -- checked in 'fsrfs' */
>  	while (endtime > time(0)) {
>  		pid_t pid;
> -		if (fs == fsend)
> -			fs = fsbase;
> -		if (fs->npass == npasses) {
> -			fsrprintf(_("Completed all %d passes\n"), npasses);
> -			break;
> -		}
>  		if (npasses > 1 && !fs->npass)
>  			Mflag = 1;
>  		else
> @@ -631,6 +625,12 @@ fsrallfs(char *mtab, int howlong, char *leftofffile)
>  		startino = 0;  /* reset after the first time through */
>  		fs->npass++;
>  		fs++;
> +		if (fs == fsend)
> +			fs = fsbase;
> +		if (fs->npass == npasses) {
> +			fsrprintf(_("Completed all %d passes\n"), npasses);
> +			break;
> +		}
>  	}
>  	fsrall_cleanup(endtime <= time(0));
>  }
> 
> 
> 


-- 
Jeff Mahoney
SUSE Labs


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2017-06-21 21:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 18:20 [PATCH] fsr: fix uninitialized fs usage after timeout Jeff Mahoney
2017-06-21 19:28 ` Eric Sandeen
2017-06-21 21:49   ` Jeff Mahoney [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=07b82f1b-040f-b472-12f8-fa9eeaf9508f@suse.com \
    --to=jeffm@suse.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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).