From: Carlos Maiolino <cmaiolino@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: fix buffer shudown reference count mismatch
Date: Tue, 30 Oct 2012 18:03:33 -0200 [thread overview]
Message-ID: <20121030200333.GA5899@andromeda.usersys.redhat.com> (raw)
In-Reply-To: <1351556454-29723-1-git-send-email-david@fromorbit.com>
On Tue, Oct 30, 2012 at 11:20:54AM +1100, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> When we shut down the filesystem, we have to unpin and free all the
> buffers currently active in the CIL. To do this we unpin and remove
> them in one operation as a result of a failed iclogbuf write. For
> buffers, we do this removal via a simultated IO completion of after
> marking the buffer stale.
>
> At the time we do this, we have two references to the buffer - the
> active LRU reference and the buf log item. The LRU reference is
> removed by marking the buffer stale, and the active CIL reference is
> by the xfs_buf_iodone() callback that is run by
> xfs_buf_do_callbacks() during ioend processing (via the bp->b_iodone
> callback).
>
> However, ioend processing requires one more reference - that of the
> IO that it is completing. We don't have this reference, so we free
> the buffer prematurely and use it after it is freed. This leads to
> assert failures in xfs_buf_rele() on debug kernels because the
> b_hold count is zero.
>
> Fix this by making sure we take the necessary IO reference before
> starting IO completion processing on the stale buffer.
>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> ---
> fs/xfs/xfs_buf_item.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/fs/xfs/xfs_buf_item.c b/fs/xfs/xfs_buf_item.c
> index a8d0ed9..b72fe88 100644
> --- a/fs/xfs/xfs_buf_item.c
> +++ b/fs/xfs/xfs_buf_item.c
> @@ -526,7 +526,23 @@ xfs_buf_item_unpin(
> }
> xfs_buf_relse(bp);
> } else if (freed && remove) {
> + /*
> + * There are currently two references to the buffer - the active
> + * LRU reference and the buf log item. What we are about to do
> + * here - simulate a failed IO completion - requires 3
> + * references.
> + *
> + * The LRU reference is removed by the xfs_buf_stale() call. The
> + * buf item reference is removed by the xfs_buf_iodone()
> + * callback that is run by xfs_buf_do_callbacks() during ioend
> + * processing (via the bp->b_iodone callback), and then finally
> + * the ioend processing drops the IO reference.
> + *
> + * Hence we need to take an additional reference here so that IO
> + * completion processing doesn't free the buffer prematurely.
> + */
> xfs_buf_lock(bp);
> + xfs_buf_hold(bp);
> xfs_buf_ioerror(bp, EIO);
> XFS_BUF_UNDONE(bp);
> xfs_buf_stale(bp);
> --
> 1.7.10
>
Looks good
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
--
--Carlos
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-10-30 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 0:20 [PATCH] xfs: fix buffer shudown reference count mismatch Dave Chinner
2012-10-30 19:26 ` Christoph Hellwig
2012-10-30 20:03 ` Carlos Maiolino [this message]
2012-10-31 17:09 ` Mark Tinguely
2012-11-01 1:26 ` 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=20121030200333.GA5899@andromeda.usersys.redhat.com \
--to=cmaiolino@redhat.com \
--cc=david@fromorbit.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.