From: Nathan Scott <nscott@aconex.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: Review: prevent deadlock via async iput from xfs_iunpin
Date: Wed, 04 Oct 2006 08:17:19 +1000 [thread overview]
Message-ID: <1159913839.32536.4.camel@edge> (raw)
In-Reply-To: <20061003050654.GQ4695059@melbourne.sgi.com>
On Tue, 2006-10-03 at 15:06 +1000, David Chinner wrote:
> In fixing the recent problems with inode use-after-free in
> xfs_iunpin, we introduced a new deadlock. When iput() is called, it
> can trigger new transactions on the inode if we are dropping the
> final reference. This is a bad thing to do from a xfslogd because it
> is theonly thread that can move the tail of the log forwards.
*nod*, sounds reasonable & your fix looks good to me, Dave.
cheers.
--
Nathan
prev parent reply other threads:[~2006-10-03 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 5:06 Review: prevent deadlock via async iput from xfs_iunpin David Chinner
2006-10-03 22:17 ` Nathan Scott [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=1159913839.32536.4.camel@edge \
--to=nscott@aconex.com \
--cc=dgc@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