From: Brian Foster <bfoster@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xfs@vger.kernel.org, Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH 2/7] xfs: remove dead code from xfs_log_unmount_write
Date: Fri, 6 Mar 2020 11:10:15 -0500 [thread overview]
Message-ID: <20200306161015.GE2773@bfoster> (raw)
In-Reply-To: <20200306143137.236478-3-hch@lst.de>
On Fri, Mar 06, 2020 at 07:31:32AM -0700, Christoph Hellwig wrote:
> When the log is shut down all iclogs are in the XLOG_STATE_IOERROR state,
> which means that xlog_state_want_sync and xlog_state_release_iclog are
> no-ops. Remove the whole section of code.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
Reviewed-by: Brian Foster <bfoster@redhat.com>
> fs/xfs/xfs_log.c | 35 +++--------------------------------
> 1 file changed, 3 insertions(+), 32 deletions(-)
>
> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> index fa499ddedb94..b56432d4a9b8 100644
> --- a/fs/xfs/xfs_log.c
> +++ b/fs/xfs/xfs_log.c
> @@ -984,38 +984,9 @@ xfs_log_unmount_write(xfs_mount_t *mp)
> iclog = iclog->ic_next;
> } while (iclog != first_iclog);
> #endif
> - if (! (XLOG_FORCED_SHUTDOWN(log))) {
> - xfs_log_write_unmount_record(mp);
> - } else {
> - /*
> - * We're already in forced_shutdown mode, couldn't
> - * even attempt to write out the unmount transaction.
> - *
> - * Go through the motions of sync'ing and releasing
> - * the iclog, even though no I/O will actually happen,
> - * we need to wait for other log I/Os that may already
> - * be in progress. Do this as a separate section of
> - * code so we'll know if we ever get stuck here that
> - * we're in this odd situation of trying to unmount
> - * a file system that went into forced_shutdown as
> - * the result of an unmount..
> - */
> - spin_lock(&log->l_icloglock);
> - iclog = log->l_iclog;
> - atomic_inc(&iclog->ic_refcnt);
> - xlog_state_want_sync(log, iclog);
> - xlog_state_release_iclog(log, iclog);
> - switch (iclog->ic_state) {
> - case XLOG_STATE_ACTIVE:
> - case XLOG_STATE_DIRTY:
> - case XLOG_STATE_IOERROR:
> - spin_unlock(&log->l_icloglock);
> - break;
> - default:
> - xlog_wait(&iclog->ic_force_wait, &log->l_icloglock);
> - break;
> - }
> - }
> + if (XLOG_FORCED_SHUTDOWN(log))
> + return;
> + xfs_log_write_unmount_record(mp);
> }
>
> /*
> --
> 2.24.1
>
next prev parent reply other threads:[~2020-03-06 16:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 14:31 cleanup log I/O error handling Christoph Hellwig
2020-03-06 14:31 ` [PATCH 1/7] xfs: remove the unused return value from xfs_log_unmount_write Christoph Hellwig
2020-03-06 16:09 ` Brian Foster
2020-03-09 8:02 ` Christoph Hellwig
2020-03-10 22:28 ` Dave Chinner
2020-03-10 22:45 ` Darrick J. Wong
2020-03-11 5:59 ` Christoph Hellwig
2020-03-06 14:31 ` [PATCH 2/7] xfs: remove dead code " Christoph Hellwig
2020-03-06 16:10 ` Brian Foster [this message]
2020-03-06 14:31 ` [PATCH 3/7] xfs: cleanup xfs_log_unmount_write Christoph Hellwig
2020-03-06 16:12 ` Brian Foster
2020-03-06 14:31 ` [PATCH 4/7] xfs: remove the aborted parameter to xlog_state_done_syncing Christoph Hellwig
2020-03-06 17:12 ` Brian Foster
2020-03-09 8:03 ` Christoph Hellwig
2020-03-06 14:31 ` [PATCH 5/7] xfs: factor out a xlog_state_activate_iclog helper Christoph Hellwig
2020-03-06 17:12 ` Brian Foster
2020-03-09 8:03 ` Christoph Hellwig
2020-03-06 14:31 ` [PATCH 6/7] xfs: cleanup xlog_state_clean_iclog Christoph Hellwig
2020-03-06 17:12 ` Brian Foster
2020-03-06 14:31 ` [PATCH 7/7] xfs: kill XLOG_STATE_IOERROR Christoph Hellwig
2020-03-06 17:15 ` Brian Foster
2020-03-09 8:05 ` Christoph Hellwig
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=20200306161015.GE2773@bfoster \
--to=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--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 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.