From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Carlos Maiolino <cmaiolino@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [RFC PATCH] xfs: Properly retry failed dquot items in case of error during buffer writeback
Date: Fri, 25 Aug 2017 10:04:01 -0700 [thread overview]
Message-ID: <20170825170400.GS4796@magnolia> (raw)
In-Reply-To: <20170825120752.22553-1-cmaiolino@redhat.com>
On Fri, Aug 25, 2017 at 02:07:52PM +0200, Carlos Maiolino wrote:
> Hi,
>
> Once the fix for inode item writeback errors is already queued
> (d3a304b62), I believe it's time to fix the same problem in dquot code.
>
> Although there were no reports of users hitting this bug in dquot code
> (at least none I've seen), the bug is there and I was already planning
> to fix it when the correct approach to fix the inodes part was decided.
>
> So, this is an RFC patch to fix the same problem in dquot code,
> regarding failed buffers being unable to be resubmitted once they are
> flush locked.
>
> The semantics are quite similar to inode items path, although during
> xfs_qm_dqflush_done(), I'm not sure if the changes I made are correct.
>
> Comments much appreciated :)
>
>
> BTW, This patch should be applied only over branch xfs-4.14-merge, it requires
> my previous patches, which are not in the master branch yet.
Looks ok, but is there an xfstests case to cover this?
--D
>
> Cheers.
>
> Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
> ---
> fs/xfs/xfs_dquot.c | 11 ++++++++---
> fs/xfs/xfs_dquot_item.c | 37 +++++++++++++++++++++++++++++++++++--
> 2 files changed, 43 insertions(+), 5 deletions(-)
>
> diff --git a/fs/xfs/xfs_dquot.c b/fs/xfs/xfs_dquot.c
> index fd2ef8c2c9a7..8198c20212a2 100644
> --- a/fs/xfs/xfs_dquot.c
> +++ b/fs/xfs/xfs_dquot.c
> @@ -987,14 +987,19 @@ xfs_qm_dqflush_done(
> * holding the lock before removing the dquot from the AIL.
> */
> if ((lip->li_flags & XFS_LI_IN_AIL) &&
> - lip->li_lsn == qip->qli_flush_lsn) {
> + (lip->li_lsn == qip->qli_flush_lsn) ||
> + lip->li_flags & XFS_LI_FAILED) {
>
> /* xfs_trans_ail_delete() drops the AIL lock. */
> spin_lock(&ailp->xa_lock);
> - if (lip->li_lsn == qip->qli_flush_lsn)
> + if (lip->li_lsn == qip->qli_flush_lsn) {
> xfs_trans_ail_delete(ailp, lip, SHUTDOWN_CORRUPT_INCORE);
> - else
> + } else if (lip->li_flags & XFS_LI_FAILED) {
> + xfs_clear_li_failed(lip);
> spin_unlock(&ailp->xa_lock);
> + } else {
> + spin_unlock(&ailp->xa_lock);
> + }
> }
>
> /*
> diff --git a/fs/xfs/xfs_dquot_item.c b/fs/xfs/xfs_dquot_item.c
> index 2c7a1629e064..35fd6d71bc42 100644
> --- a/fs/xfs/xfs_dquot_item.c
> +++ b/fs/xfs/xfs_dquot_item.c
> @@ -137,6 +137,23 @@ xfs_qm_dqunpin_wait(
> wait_event(dqp->q_pinwait, (atomic_read(&dqp->q_pincount) == 0));
> }
>
> +/*
> + * Callback used to mark a buffer with XFS_LI_FAILED when items in the buffer
> + * have been failed during writeback
> + *
> + * this informs the AIL that the dquot is already flush locked on the next push,
> + * and acquires a hold on the buffer to ensure that it isn't reclaimed before
> + * dirty data makes it to disk.
> + */
> +STATIC void
> +xfs_dquot_item_error(
> + struct xfs_log_item *lip,
> + struct xfs_buf *bp)
> +{
> + ASSERT(XFS_DQ_IS_LOCKED(DQUOT_ITEM(lip)->qli_item));
> + xfs_set_li_failed(lip, bp);
> +}
> +
> STATIC uint
> xfs_qm_dquot_logitem_push(
> struct xfs_log_item *lip,
> @@ -144,13 +161,28 @@ xfs_qm_dquot_logitem_push(
> __acquires(&lip->li_ailp->xa_lock)
> {
> struct xfs_dquot *dqp = DQUOT_ITEM(lip)->qli_dquot;
> - struct xfs_buf *bp = NULL;
> + struct xfs_buf *bp = lip->li_buf;
> uint rval = XFS_ITEM_SUCCESS;
> int error;
>
> if (atomic_read(&dqp->q_pincount) > 0)
> return XFS_ITEM_PINNED;
>
> + /*
> + * The buffer containing this item failed to be written back
> + * previously. Resubmit the buffer for IO
> + */
> + if (lip->li_flags & XFS_LI_FAILED) {
> + if (!xfs_buf_trylock(bp))
> + return XFS_ITEM_LOCKED;
> +
> + if (!xfs_buf_resubmit_failed_buffers(bp, lip, buffer_list))
> + rval = XFS_ITEM_FLUSHING;
> +
> + xfs_buf_unlock(bp);
> + return rval;
> + }
> +
> if (!xfs_dqlock_nowait(dqp))
> return XFS_ITEM_LOCKED;
>
> @@ -242,7 +274,8 @@ static const struct xfs_item_ops xfs_dquot_item_ops = {
> .iop_unlock = xfs_qm_dquot_logitem_unlock,
> .iop_committed = xfs_qm_dquot_logitem_committed,
> .iop_push = xfs_qm_dquot_logitem_push,
> - .iop_committing = xfs_qm_dquot_logitem_committing
> + .iop_committing = xfs_qm_dquot_logitem_committing,
> + .iop_error = xfs_dquot_item_error
> };
>
> /*
> --
> 2.13.5
>
> --
> 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
next prev parent reply other threads:[~2017-08-25 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 12:07 [RFC PATCH] xfs: Properly retry failed dquot items in case of error during buffer writeback Carlos Maiolino
2017-08-25 17:04 ` Darrick J. Wong [this message]
2017-08-25 21:57 ` Darrick J. Wong
2017-08-28 9:20 ` Carlos Maiolino
2017-10-13 16:21 ` Darrick J. Wong
2017-11-20 15:03 ` Carlos Maiolino
2017-10-16 3:05 ` Hou Tao
2017-10-16 18:49 ` Darrick J. Wong
2017-11-20 15:04 ` Carlos Maiolino
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=20170825170400.GS4796@magnolia \
--to=darrick.wong@oracle.com \
--cc=cmaiolino@redhat.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;
as well as URLs for NNTP newsgroup(s).