| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 3/5] xfs: asserting lock not held during freeing not valid |
| From: | Mark Tinguely <tinguely@xxxxxxx> |
| Date: | Tue, 24 Sep 2013 12:17:09 -0500 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <1380002476-18839-4-git-send-email-david@xxxxxxxxxxxxx> |
| References: | <1380002476-18839-1-git-send-email-david@xxxxxxxxxxxxx> <1380002476-18839-4-git-send-email-david@xxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120122 Thunderbird/9.0 |
On 09/24/13 01:01, Dave Chinner wrote: From: Dave Chinner<dchinner@xxxxxxxxxx> When we free an inode, we do so via RCU. As an RCU lookup can occur at any time before we free an inode, and that lookup takes the inode flags lock, we cannot safely assert that the flags lock is not held just before marking it dead and running call_rcu() to free the inode. We check on allocation of a new inode structre that the lock is not held, so we still have protection against locks being leaked and hence not correctly initialised when allocated out of the slab. Hence just remove the assert... Signed-off-by: Dave Chinner<dchinner@xxxxxxxxxx> --- Looks good. Reviewed-by: Mark Tinguely <tinguely@xxxxxxx> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 5/5] xfs: log recovery lsn ordering needs uuid check, Ben Myers |
|---|---|
| Next by Date: | Re: [PATCH] xfs: v2 fix node forward in xfs_node_toosmall, Mark Tinguely |
| Previous by Thread: | [PATCH 3/5] xfs: asserting lock not held during freeing not valid, Dave Chinner |
| Next by Thread: | [PATCH 4/5] xfs: fix XFS_IOC_FREE_EOFBLOCKS definition, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |