From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 4/8] xfs: factor debug code out of xlog_state_do_callback()
Date: Thu, 5 Sep 2019 08:30:06 -0700 [thread overview]
Message-ID: <20190905153006.GE2229799@magnolia> (raw)
In-Reply-To: <20190905084717.30308-5-david@fromorbit.com>
On Thu, Sep 05, 2019 at 06:47:13PM +1000, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> Start making this function readable by lifting the debug code into
> a conditional function.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> ---
> fs/xfs/xfs_log.c | 79 +++++++++++++++++++++++++++---------------------
> 1 file changed, 44 insertions(+), 35 deletions(-)
>
> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> index 8380ed065608..2904bf0d17f3 100644
> --- a/fs/xfs/xfs_log.c
> +++ b/fs/xfs/xfs_log.c
> @@ -2628,6 +2628,48 @@ xlog_get_lowest_lsn(
> return lowest_lsn;
> }
>
> +#ifdef DEBUG
> +/*
> + * Make one last gasp attempt to see if iclogs are being left in limbo. If the
> + * above loop finds an iclog earlier than the current iclog and in one of the
> + * syncing states, the current iclog is put into DO_CALLBACK and the callbacks
> + * are deferred to the completion of the earlier iclog. Walk the iclogs in order
> + * and make sure that no iclog is in DO_CALLBACK unless an earlier iclog is in
> + * one of the syncing states.
> + *
> + * Note that SYNCING|IOERROR is a valid state so we cannot just check for
> + * ic_state == SYNCING.
> + */
> +static void
> +xlog_state_callback_check_state(
> + struct xlog *log)
> +{
> + struct xlog_in_core *first_iclog = log->l_iclog;
> + struct xlog_in_core *iclog = first_iclog;
> +
> + do {
> + ASSERT(iclog->ic_state != XLOG_STATE_DO_CALLBACK);
> + /*
> + * Terminate the loop if iclogs are found in states
> + * which will cause other threads to clean up iclogs.
> + *
> + * SYNCING - i/o completion will go through logs
> + * DONE_SYNC - interrupt thread should be waiting for
> + * l_icloglock
> + * IOERROR - give up hope all ye who enter here
> + */
> + if (iclog->ic_state == XLOG_STATE_WANT_SYNC ||
> + iclog->ic_state & XLOG_STATE_SYNCING ||
Code like this make my eyes twitch (Does ic_state track mutually
exclusive state? Or is it state flags? I think it's the second!),
but as this is simply refactoring debugging code...
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> + iclog->ic_state == XLOG_STATE_DONE_SYNC ||
> + iclog->ic_state == XLOG_STATE_IOERROR )
> + break;
> + iclog = iclog->ic_next;
> + } while (first_iclog != iclog);
> +}
> +#else
> +#define xlog_state_callback_check_state(l) ((void)0)
> +#endif
> +
> STATIC void
> xlog_state_do_callback(
> struct xlog *log,
> @@ -2802,41 +2844,8 @@ xlog_state_do_callback(
> }
> } while (!ioerrors && loopdidcallbacks);
>
> -#ifdef DEBUG
> - /*
> - * Make one last gasp attempt to see if iclogs are being left in limbo.
> - * If the above loop finds an iclog earlier than the current iclog and
> - * in one of the syncing states, the current iclog is put into
> - * DO_CALLBACK and the callbacks are deferred to the completion of the
> - * earlier iclog. Walk the iclogs in order and make sure that no iclog
> - * is in DO_CALLBACK unless an earlier iclog is in one of the syncing
> - * states.
> - *
> - * Note that SYNCING|IOABORT is a valid state so we cannot just check
> - * for ic_state == SYNCING.
> - */
> - if (funcdidcallbacks) {
> - first_iclog = iclog = log->l_iclog;
> - do {
> - ASSERT(iclog->ic_state != XLOG_STATE_DO_CALLBACK);
> - /*
> - * Terminate the loop if iclogs are found in states
> - * which will cause other threads to clean up iclogs.
> - *
> - * SYNCING - i/o completion will go through logs
> - * DONE_SYNC - interrupt thread should be waiting for
> - * l_icloglock
> - * IOERROR - give up hope all ye who enter here
> - */
> - if (iclog->ic_state == XLOG_STATE_WANT_SYNC ||
> - iclog->ic_state & XLOG_STATE_SYNCING ||
> - iclog->ic_state == XLOG_STATE_DONE_SYNC ||
> - iclog->ic_state == XLOG_STATE_IOERROR )
> - break;
> - iclog = iclog->ic_next;
> - } while (first_iclog != iclog);
> - }
> -#endif
> + if (funcdidcallbacks)
> + xlog_state_callback_check_state(log);
>
> if (log->l_iclog->ic_state & (XLOG_STATE_ACTIVE|XLOG_STATE_IOERROR))
> wake_up_all(&log->l_flush_wait);
> --
> 2.23.0.rc1
>
next prev parent reply other threads:[~2019-09-05 15:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 8:47 [PATCH 1/8 v2] xfs: log race fixes and cleanups Dave Chinner
2019-09-05 8:47 ` [PATCH 1/8] xfs: push the AIL in xlog_grant_head_wake Dave Chinner
2019-09-05 15:18 ` Darrick J. Wong
2019-09-05 22:02 ` Dave Chinner
2019-09-05 8:47 ` [PATCH 2/8] xfs: fix missed wakeup on l_flush_wait Dave Chinner
2019-09-05 15:21 ` Darrick J. Wong
2019-09-05 8:47 ` [PATCH 3/8] xfs: prevent CIL push holdoff in log recovery Dave Chinner
2019-09-05 15:26 ` Darrick J. Wong
2019-09-05 22:10 ` Dave Chinner
2019-09-05 8:47 ` [PATCH 4/8] xfs: factor debug code out of xlog_state_do_callback() Dave Chinner
2019-09-05 15:30 ` Darrick J. Wong [this message]
2019-09-05 22:14 ` Dave Chinner
2019-09-05 8:47 ` [PATCH 5/8] xfs: factor callbacks " Dave Chinner
2019-09-05 15:39 ` Darrick J. Wong
2019-09-05 22:17 ` Dave Chinner
2019-09-05 8:47 ` [PATCH 6/8] xfs: factor iclog state processing " Dave Chinner
2019-09-05 15:45 ` Darrick J. Wong
2019-09-05 8:47 ` [PATCH 7/8] xfs: push iclog state cleaning into xlog_state_clean_log Dave Chinner
2019-09-05 15:48 ` Darrick J. Wong
2019-09-05 22:28 ` Dave Chinner
2019-09-05 8:47 ` [PATCH 8/8] xfs: push the grant head when the log head moves forward Dave Chinner
2019-09-05 16:00 ` Darrick J. Wong
2019-09-05 15:44 ` [PATCH 1/8 v2] xfs: log race fixes and cleanups Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2019-09-06 0:05 [PATCH0/8 v3] " Dave Chinner
2019-09-06 0:05 ` [PATCH 4/8] xfs: factor debug code out of xlog_state_do_callback() Dave Chinner
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=20190905153006.GE2229799@magnolia \
--to=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--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