From: Lachlan McIlroy <lachlan@sgi.com>
To: lachlan@sgi.com
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH V2] make inode reclaim wait for log I/O to complete
Date: Wed, 18 Jun 2008 14:26:19 +1000 [thread overview]
Message-ID: <48588E6B.3010006@sgi.com> (raw)
In-Reply-To: <48364E43.3030108@sgi.com>
ping.
Lachlan McIlroy wrote:
> During a forced shutdown a xfs inode can be destroyed before log
> I/O involving that inode is complete. We need to wait for the
> inode to be unpinned before tearing it down. Version 2 cleans up
> the code a bit by relying on xfs_iflush() to do the unpinning and
> forced shutdown check.
>
> --- fs/xfs/xfs_inode.c_1.504 2008-05-23 11:19:21.000000000 +1000
> +++ fs/xfs/xfs_inode.c 2008-05-23 11:21:14.000000000 +1000
> @@ -3082,8 +3082,6 @@ xfs_iflush(
> * flush lock and do nothing.
> */
> if (xfs_inode_clean(ip)) {
> - ASSERT((iip != NULL) ?
> - !(iip->ili_item.li_flags & XFS_LI_IN_AIL) : 1);
> xfs_ifunlock(ip);
> return 0;
> }
> --- fs/xfs/xfs_vnodeops.c_1.760 2008-05-22 16:01:09.000000000 +1000
> +++ fs/xfs/xfs_vnodeops.c 2008-05-23 11:52:54.000000000 +1000
> @@ -3260,7 +3260,6 @@ xfs_finish_reclaim(
> {
> xfs_perag_t *pag = xfs_get_perag(ip->i_mount, ip->i_ino);
> bhv_vnode_t *vp = XFS_ITOV_NULL(ip);
> - int error;
>
> if (vp && VN_BAD(vp))
> goto reclaim;
> @@ -3303,29 +3302,16 @@ xfs_finish_reclaim(
> xfs_iflock(ip);
> }
>
> - if (!XFS_FORCED_SHUTDOWN(ip->i_mount)) {
> - if (ip->i_update_core ||
> - ((ip->i_itemp != NULL) &&
> - (ip->i_itemp->ili_format.ilf_fields != 0))) {
> - error = xfs_iflush(ip, sync_mode);
> - /*
> - * If we hit an error, typically because of filesystem
> - * shutdown, we don't need to let vn_reclaim to know
> - * because we're gonna reclaim the inode anyway.
> - */
> - if (error) {
> - xfs_iunlock(ip, XFS_ILOCK_EXCL);
> - goto reclaim;
> - }
> - xfs_iflock(ip); /* synchronize with xfs_iflush_done */
> - }
> -
> - ASSERT(ip->i_update_core == 0);
> - ASSERT(ip->i_itemp == NULL ||
> - ip->i_itemp->ili_format.ilf_fields == 0);
> + /*
> + * In the case of a forced shutdown we rely on xfs_iflush() to
> + * wait for the inode to be unpinned before returning an error.
> + */
> + if (xfs_iflush(ip, sync_mode) == 0) {
> + /* synchronize with xfs_iflush_done */
> + xfs_iflock(ip);
> + xfs_ifunlock(ip);
> }
>
> - xfs_ifunlock(ip);
> xfs_iunlock(ip, XFS_ILOCK_EXCL);
>
> reclaim:
>
>
>
next prev parent reply other threads:[~2008-06-18 4:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 4:55 [PATCH V2] make inode reclaim wait for log I/O to complete Lachlan McIlroy
2008-06-18 4:26 ` Lachlan McIlroy [this message]
2008-06-18 4:30 ` Dave Chinner
2008-06-18 6:40 ` 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=48588E6B.3010006@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.