linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Eryu Guan <guaneryu@gmail.com>
Cc: linux-xfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: undo block reservation correctly in xfs_trans_reserve()
Date: Tue, 6 Sep 2016 18:48:28 +1000	[thread overview]
Message-ID: <20160906084828.GK30056@dastard> (raw)
In-Reply-To: <1473149039-30487-1-git-send-email-guaneryu@gmail.com>

On Tue, Sep 06, 2016 at 04:03:59PM +0800, Eryu Guan wrote:
> "blocks" should be added back to fdblocks at undo time, not taken
> away, i.e. the minus sign should not be used.

You've described the code change you made, not about the problem you
hit and are fixing.

i.e. I've got no idea how you found this, or even how to identify a
system that is tripping over this problem. By describing how you
found it and the symptoms being displayed, I'll learn from you how
to identify the problem and hence, in future, be able to identify
systems that are tripping over the problem, too.

> Fixes: 0d485ada404b ("xfs: use generic percpu counters for free block counter")

I really don't like this sort of "annotation". It wrongly implies
the commit was broken (it wasn't) and there's no scope for stating
the problem context. i.e.  that the problem is a minor regression in
a rarely travelled corner case that is unlikely to affect production
machines in any significant way. It's better to describe things with
all the relevant context:

"This is a regression introduced in commit ... and only occurs when
.... "

> Signed-off-by: Eryu Guan <guaneryu@gmail.com>

Not @redhat?

> ---
>  fs/xfs/xfs_trans.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/xfs/xfs_trans.c b/fs/xfs/xfs_trans.c
> index 5f3d33d..011dace 100644
> --- a/fs/xfs/xfs_trans.c
> +++ b/fs/xfs/xfs_trans.c
> @@ -217,7 +217,7 @@ undo_log:
>  
>  undo_blocks:
>  	if (blocks > 0) {
> -		xfs_mod_fdblocks(tp->t_mountp, -((int64_t)blocks), rsvd);
> +		xfs_mod_fdblocks(tp->t_mountp, ((int64_t)blocks), rsvd);

Outer () can be dropped, too.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2016-09-06  8:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06  8:03 [PATCH] xfs: undo block reservation correctly in xfs_trans_reserve() Eryu Guan
2016-09-06  8:48 ` Dave Chinner [this message]
2016-09-06 11:50   ` Eryu Guan
2016-09-06 22:35     ` Dave Chinner

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=20160906084828.GK30056@dastard \
    --to=david@fromorbit.com \
    --cc=guaneryu@gmail.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=xfs@oss.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;
as well as URLs for NNTP newsgroup(s).