From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: fix race in inode cluster freeing failing to stale inodes
Date: Tue, 25 May 2010 12:40:52 -0400 [thread overview]
Message-ID: <20100525164052.GA18666@infradead.org> (raw)
In-Reply-To: <1274581478-19260-1-git-send-email-david@fromorbit.com>
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.
*/
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-05-25 16:38 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 [this message]
2010-05-25 22:58 ` 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=20100525164052.GA18666@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--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