From: Christoph Hellwig <hch@infradead.org>
To: Lachlan McIlroy <lachlan@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH V2] Unlock inode before calling xfs_idestroy()
Date: Mon, 22 Sep 2008 03:51:55 -0400 [thread overview]
Message-ID: <20080922075155.GA14024@infradead.org> (raw)
In-Reply-To: <48D72864.2020604@sgi.com>
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 parent reply other threads:[~2008-09-22 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 5:08 [PATCH V2] Unlock inode before calling xfs_idestroy() Lachlan McIlroy
2008-09-22 7:51 ` Christoph Hellwig [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=20080922075155.GA14024@infradead.org \
--to=hch@infradead.org \
--cc=lachlan@sgi.com \
--cc=xfs-dev@sgi.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