From: Christoph Hellwig <hch@lst.de>
To: xfs@oss.sgi.com
Subject: locking in xfs_unmount_flush
Date: Fri, 23 May 2008 12:22:39 +0200 [thread overview]
Message-ID: <20080523102238.GA18456@lst.de> (raw)
Does anybody have an idea why the ilock on the root inode is held
over flushing and releasing of the rt and quota inodes in
xfs_unmount_flush? I've looked through all that code and can't find
any reason why we'd want it.
reply other threads:[~2008-05-23 10:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080523102238.GA18456@lst.de \
--to=hch@lst.de \
--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