From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/3] xfs: clear MS_ACTIVE after finishing log recovery
Date: Wed, 16 Aug 2017 07:56:58 -0400 [thread overview]
Message-ID: <20170816115658.GB54738@bfoster.bfoster> (raw)
In-Reply-To: <150274842319.16269.6356165894145725007.stgit@magnolia>
On Mon, Aug 14, 2017 at 03:07:03PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Way back when we established inode block-map redo log items, it was
> discovered that we needed to prevent the VFS from evicting inodes during
> log recovery because any given inode might be have bmap redo items to
> replay even if the inode has no link count and is ultimately deleted,
> and any eviction of an unlinked inode causes the inode to be truncated
> and freed too early.
>
> To make this possible, we set MS_ACTIVE so that inodes would not be torn
> down immediately upon release. Unfortunately, this also results in the
> quota inodes not being released at all if a later part of the mount
> process should fail, because we never reclaim the inodes. So, set
> MS_ACTIVE right before we do the last part of log recovery and clear it
> immediately after we finish the log recovery so that everything
> will be torn down properly if we abort the mount.
>
> Fixes: 17c12bcd30 ("xfs: when replaying bmap operations, don't let unlinked inodes get reaped")
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
Reviewed-by: Brian Foster <bfoster@redhat.com>
> fs/xfs/xfs_log.c | 11 +++++++++++
> fs/xfs/xfs_mount.c | 10 ----------
> 2 files changed, 11 insertions(+), 10 deletions(-)
>
>
> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> index 0053bcf..4ebd0ba 100644
> --- a/fs/xfs/xfs_log.c
> +++ b/fs/xfs/xfs_log.c
> @@ -749,9 +749,20 @@ xfs_log_mount_finish(
> return 0;
> }
>
> + /*
> + * During the second phase of log recovery, we need iget and
> + * iput to behave like they do for an active filesystem.
> + * xfs_fs_drop_inode needs to be able to prevent the deletion
> + * of inodes before we're done replaying log items on those
> + * inodes. Turn it off immediately after recovery finishes
> + * so that we don't leak the quota inodes if subsequent mount
> + * activities fail.
> + */
> + mp->m_super->s_flags |= MS_ACTIVE;
> error = xlog_recover_finish(mp->m_log);
> if (!error)
> xfs_log_work_queue(mp);
> + mp->m_super->s_flags &= ~MS_ACTIVE;
>
> return error;
> }
> diff --git a/fs/xfs/xfs_mount.c b/fs/xfs/xfs_mount.c
> index 40d4e8b..151a82db 100644
> --- a/fs/xfs/xfs_mount.c
> +++ b/fs/xfs/xfs_mount.c
> @@ -945,15 +945,6 @@ xfs_mountfs(
> }
>
> /*
> - * During the second phase of log recovery, we need iget and
> - * iput to behave like they do for an active filesystem.
> - * xfs_fs_drop_inode needs to be able to prevent the deletion
> - * of inodes before we're done replaying log items on those
> - * inodes.
> - */
> - mp->m_super->s_flags |= MS_ACTIVE;
> -
> - /*
> * Finish recovering the file system. This part needed to be delayed
> * until after the root and real-time bitmap inodes were consistently
> * read in.
> @@ -1028,7 +1019,6 @@ xfs_mountfs(
> out_quota:
> xfs_qm_unmount_quotas(mp);
> out_rtunmount:
> - mp->m_super->s_flags &= ~MS_ACTIVE;
> xfs_rtunmount_inodes(mp);
> out_rele_rip:
> IRELE(rip);
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-08-16 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 22:07 [PATCH 1/3] xfs: clear MS_ACTIVE after finishing log recovery Darrick J. Wong
2017-08-14 22:07 ` [PATCH 2/3] xfs: don't leak quotacheck dquots when cow recovery Darrick J. Wong
2017-08-14 22:07 ` [PATCH 3/3] xfs: evict all inodes involved with log redo item Darrick J. Wong
2017-08-15 2:16 ` Dave Chinner
2017-08-15 4:03 ` Darrick J. Wong
2017-08-16 11:57 ` Brian Foster
2017-08-16 11:56 ` Brian Foster [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=20170816115658.GB54738@bfoster.bfoster \
--to=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).