public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: fix race in inode cluster freeing failing to stale inodes
Date: Wed, 26 May 2010 08:58:29 +1000	[thread overview]
Message-ID: <20100525225829.GO2150@dastard> (raw)
In-Reply-To: <20100525164052.GA18666@infradead.org>

On Tue, May 25, 2010 at 12:40:52PM -0400, Christoph Hellwig wrote:
> Looks good, but some minor nits on the comments below:
> 
> 
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> 
> >  		/*
> > +		 * Now we've locked out tail pushing and flushing by locking
> > +		 * the buffer, look for each inode in memory and attempt to
> > +		 * lock it. Any inode we get the locks on add it to the inode
> > +		 * buffer and set it up for being staled on buffer IO
> > +		 * completion.
> 
> This comment reads a bit odd.  The first thing we do in the loop is
> locking the buffer, so the "Now" at the beginning of the comment feels
> rather out of place.  What about:
> 
> 		/*
> 		 * For each inode in memory attempt to add it to the inode
> 		 * buffer and set it up for being staled on buffer IO
> 		 * completion.  This is safe as we've locked out tail
> 		 * pushing and flushing by locking the buffer.
> 		 *
> 		 * We have already marked every inode that was part of
> 		 * a transaction stale above, which means there is no
> 		 * point in even trying to lock them.
> 		 */

That reads better. I'll update it to match.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

      reply	other threads:[~2010-05-25 22:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-23  2:24 [PATCH] xfs: fix race in inode cluster freeing failing to stale inodes Dave Chinner
2010-05-25 16:40 ` Christoph Hellwig
2010-05-25 22:58   ` Dave Chinner [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=20100525225829.GO2150@dastard \
    --to=david@fromorbit.com \
    --cc=hch@infradead.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