| To: | Lachlan McIlroy <lachlan@xxxxxxx> |
|---|---|
| Subject: | Re: [PATCH V2] Unlock inode before calling xfs_idestroy() |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Mon, 22 Sep 2008 03:51:55 -0400 |
| Cc: | xfs-dev <xfs-dev@xxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx> |
| In-reply-to: | <48D72864.2020604@sgi.com> |
| References: | <48D72864.2020604@sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Mon, Sep 22, 2008 at 03:08:52PM +1000, Lachlan McIlroy wrote: > Lock debugging reported the ilock was being destroyed without being > unlocked. We don't need to lock the inode until we are going to > insert it into the radix tree. Looks good. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] Fix race in xfs_write() between direct and buffered I/O with DMAPI, Lachlan McIlroy |
|---|---|
| Next by Date: | TAKE 987246 - Unlock inode before calling xfs_idestroy(), Lachlan McIlroy |
| Previous by Thread: | [PATCH V2] Unlock inode before calling xfs_idestroy(), Lachlan McIlroy |
| Next by Thread: | [PATCH] Fix race in xfs_write() between direct and buffered I/O with DMAPI, Lachlan McIlroy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |