| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 1/5] xfs: fix inode validity check in xfs_iflush_cluster |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Thu, 7 Apr 2016 08:47:31 -0700 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <1459934574-25543-2-git-send-email-david@xxxxxxxxxxxxx> |
| References: | <1459934574-25543-1-git-send-email-david@xxxxxxxxxxxxx> <1459934574-25543-2-git-send-email-david@xxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.24 (2015-08-30) |
On Wed, Apr 06, 2016 at 07:22:50PM +1000, Dave Chinner wrote:
> From: Dave Chinner <dchinner@xxxxxxxxxx>
>
> Some careless idiot wrote crap code in commit 1a3e8f3 ("xfs: convert
> inode cache lookups to use RCU locking") back in late 2010, and so
> xfs_iflush_cluster checks the wrong inode for whether it is still
> valid under RCU protection. Fix it to lock and check the correct
> inode.
>
> Part of the reason for the screwup was the unconventional naming of
> the cluster inode variable - iq - so also rename all the cluster
> inode variables to use a more conventional prefixes to reduce
> potential future confusion (cilist, cilist_size, cip).
Between all that renaming I didn't actually manage to find the fix :)
Can you split the rename and the fix into separate patches?
|
| Previous by Date: | Re: [PATCH] xfs/259: handle minimum block size more precisely, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [PATCH 2/5] xfs: skip stale inodes in xfs_iflush_cluster, Christoph Hellwig |
| Previous by Thread: | Re: [PATCH 1/5] xfs: fix inode validity check in xfs_iflush_cluster, Brian Foster |
| Next by Thread: | [PATCH 2/5] xfs: skip stale inodes in xfs_iflush_cluster, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |