public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: fstests@vger.kernel.org, Dave Chinner <david@fromorbit.com>,
	Lukas Czerner <lczerner@redhat.com>,
	Allison Henderson <achender@vnet.ibm.com>,
	Christoph Hellwig <hch@lst.de>, Nathan Scott <nathans@sgi.com>
Subject: Re: [PATCH] xfstests: fix build warnings and notify_others() bug
Date: Tue, 20 Dec 2016 10:56:55 -0700	[thread overview]
Message-ID: <20161220175655.GB26994@linux.intel.com> (raw)
In-Reply-To: <20161220175534.GA26994@linux.intel.com>

On Tue, Dec 20, 2016 at 10:55:34AM -0700, Ross Zwisler wrote:
> On Tue, Dec 06, 2016 at 09:04:01PM -0700, Ross Zwisler wrote:
> > This patch addresses the following build warnings:
> > 
> > fsx.c: In function 'do_punch_hole':
> > fsx.c:940:3: warning: this 'if' clause does not guard... [-Wmisleading-indentation]
> >    if (!quiet && testcalls > simulatedopcount)
> >    ^~
> > fsx.c:942:4: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the 'if'
> > log4(OP_PUNCH_HOLE, offset, length, FL_SKIPPED);
> > ^~~~
> > fsx.c:947:3: warning: this 'if' clause does not guard... [-Wmisleading-indentation]
> >    if (!quiet && testcalls > simulatedopcount)
> >    ^~
> > fsx.c:949:4: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the 'if'
> > log4(OP_PUNCH_HOLE, offset, length, FL_SKIPPED);
> > ^~~~
> > fsx.c: In function 'do_zero_range':
> > fsx.c:995:3: warning: this 'if' clause does not guard... [-Wmisleading-indentation]
> >    if (!quiet && testcalls > simulatedopcount)
> >    ^~
> > fsx.c:997:4: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the 'if'
> > log4(OP_ZERO_RANGE, offset, length, FL_SKIPPED |
> > ^~~~
> > [CC]    growfiles
> > growfiles.c: In function 'notify_others':
> > growfiles.c:1458:6: warning: this 'if' clause does not guard... [-Wmisleading-indentation]
> >   if ( Forker_pids[ind] != Pid )
> >   ^~
> > growfiles.c:1462:10: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the 'if'
> >   kill(Forker_pids[ind], SIGUSR2);
> >   ^~~~
> > 
> > The warnings in fsx.c were just spacing issues of the form:
> > 
> > 	if (length == 0) {
> > 		if (!quiet && testcalls > simulatedopcount)
> > 			prt("skipping zero length punch hole\n");
> > 			log4(OP_PUNCH_HOLE, offset, length, FL_SKIPPED);
> > 		return;
> > 	}
> > 
> > Where the log4() call just needs to be unindented.  log4() calls elsewhere
> > in that same file are not protected with any sort of 'quiet' check, and
> > commonly follow prt() calls which are.  See doread(), domapread(), etc.
> > 
> > The warning from growfiles.c was actually a bug.  notify_others() is
> > looping through the Forker_pids[] array and sending SIGUSR2 to all other
> > processes.  However, with the current logic it only *logs* the kill for
> > other processes, and kills all other processes plus the Forker_pids[] entry
> > that matches 'Pid'.
> > 
> > Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
> > Cc: Dave Chinner <david@fromorbit.com>
> > Cc: Lukas Czerner <lczerner@redhat.com>
> > Cc: Allison Henderson <achender@vnet.ibm.com>
> > Cc: Christoph Hellwig <hch@lst.de>
> > Cc: Nathan Scott <nathans@sgi.com>
> 
> Ping on this patch.

Sorry, it was already applied.  My apologies for the noise.

      reply	other threads:[~2016-12-20 17:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07  4:04 [PATCH] xfstests: fix build warnings and notify_others() bug Ross Zwisler
2016-12-20 17:55 ` Ross Zwisler
2016-12-20 17:56   ` Ross Zwisler [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=20161220175655.GB26994@linux.intel.com \
    --to=ross.zwisler@linux.intel.com \
    --cc=achender@vnet.ibm.com \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=lczerner@redhat.com \
    --cc=nathans@sgi.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