From: Lachlan McIlroy <lachlan@sgi.com>
To: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH] make inode reclaim synchronise with xfs_iflush_done()
Date: Wed, 12 Dec 2007 18:02:37 +1100 [thread overview]
Message-ID: <475F878D.6090407@sgi.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
On a forced shutdown, xfs_finish_reclaim() will skip flushing the inode.
If the inode flush lock is not already held and there is an outstanding
xfs_iflush_done() then we might free the inode prematurely. By acquiring
and releasing the flush lock we will synchronise with xfs_iflush_done().
Alternatively we could take a hold on the inode when when issuing I/Os
with xfs_iflush_done() and release it in xfs_iflush_done(). Would this
be a better approach?
Lachlan
[-- Attachment #2: xfs_finish_reclaim.diff --]
[-- Type: text/x-patch, Size: 981 bytes --]
--- fs/xfs/xfs_vnodeops.c_1.726 2007-12-12 17:14:59.000000000 +1100
+++ fs/xfs/xfs_vnodeops.c 2007-12-12 17:15:42.000000000 +1100
@@ -3762,20 +3762,29 @@ xfs_finish_reclaim(
goto reclaim;
}
xfs_iflock(ip); /* synchronize with xfs_iflush_done */
+ xfs_ifunlock(ip);
}
ASSERT(ip->i_update_core == 0);
ASSERT(ip->i_itemp == NULL ||
ip->i_itemp->ili_format.ilf_fields == 0);
xfs_iunlock(ip, XFS_ILOCK_EXCL);
- } else if (locked) {
+ } else {
/*
* We are not interested in doing an iflush if we're
* in the process of shutting down the filesystem forcibly.
* So, just reclaim the inode.
- */
- xfs_ifunlock(ip);
- xfs_iunlock(ip, XFS_ILOCK_EXCL);
+ *
+ * If the flush lock is not already held then temporarily
+ * acquire it to synchronize with xfs_iflush_done.
+ */
+ if (locked) {
+ xfs_ifunlock(ip);
+ xfs_iunlock(ip, XFS_ILOCK_EXCL);
+ } else {
+ xfs_iflock(ip);
+ xfs_ifunlock(ip);
+ }
}
reclaim:
next reply other threads:[~2007-12-12 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 7:02 Lachlan McIlroy [this message]
2007-12-14 20:29 ` [PATCH] make inode reclaim synchronise with xfs_iflush_done() Christoph Hellwig
[not found] ` <20071212230858.GO4612@sgi.com>
2008-01-14 3:57 ` Lachlan McIlroy
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=475F878D.6090407@sgi.com \
--to=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