linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: fix and streamline error handling in xfs_end_io
Date: Mon, 27 Feb 2017 21:34:20 -0800	[thread overview]
Message-ID: <20170228053420.GG5297@birch.djwong.org> (raw)
In-Reply-To: <20170228004950.9609-1-hch@lst.de>

On Mon, Feb 27, 2017 at 04:49:50PM -0800, Christoph Hellwig wrote:
> There are two different cases of buffered I/O errors:
> 
>  - first we can have an already shutdown fs.  In that case we should skip
>    any on-disk operations and just clean up the appen transaction if
>    present and destroy the ioend
>  - a real I/O error.  In that case we should cleanup any lingering COW
>    blocks.  This gets skipped in the current code and is fixed by this
>    patch.

Somehow I lost that through all the rebasing of the reflink patchset,
thank you for catching this!

Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>

--D

> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>  fs/xfs/xfs_aops.c | 59 +++++++++++++++++++++++++------------------------------
>  1 file changed, 27 insertions(+), 32 deletions(-)
> 
> diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c
> index 290c0fb306e7..fe244648fff0 100644
> --- a/fs/xfs/xfs_aops.c
> +++ b/fs/xfs/xfs_aops.c
> @@ -274,54 +274,49 @@ xfs_end_io(
>  	struct xfs_ioend	*ioend =
>  		container_of(work, struct xfs_ioend, io_work);
>  	struct xfs_inode	*ip = XFS_I(ioend->io_inode);
> +	xfs_off_t		offset = ioend->io_offset;
> +	size_t			size = ioend->io_size;
>  	int			error = ioend->io_bio->bi_error;
>  
>  	/*
> -	 * Set an error if the mount has shut down and proceed with end I/O
> -	 * processing so it can perform whatever cleanups are necessary.
> +	 * Just clean up the in-memory strutures if the fs has been shut down.
>  	 */
> -	if (XFS_FORCED_SHUTDOWN(ip->i_mount))
> +	if (XFS_FORCED_SHUTDOWN(ip->i_mount)) {
>  		error = -EIO;
> +		goto done;
> +	}
>  
>  	/*
> -	 * For a CoW extent, we need to move the mapping from the CoW fork
> -	 * to the data fork.  If instead an error happened, just dump the
> -	 * new blocks.
> +	 * Clean up any COW blocks on an I/O error.
>  	 */
> -	if (ioend->io_type == XFS_IO_COW) {
> -		if (error)
> -			goto done;
> -		if (ioend->io_bio->bi_error) {
> -			error = xfs_reflink_cancel_cow_range(ip,
> -					ioend->io_offset, ioend->io_size, 0);
> -			goto done;
> +	if (unlikely(error)) {
> +		switch (ioend->io_type) {
> +		case XFS_IO_COW:
> +			xfs_reflink_cancel_cow_range(ip, offset, size, 0);
> +			break;
>  		}
> -		error = xfs_reflink_end_cow(ip, ioend->io_offset,
> -				ioend->io_size);
> -		if (error)
> -			goto done;
> +
> +		goto done;
>  	}
>  
>  	/*
> -	 * For unwritten extents we need to issue transactions to convert a
> -	 * range to normal written extens after the data I/O has finished.
> -	 * Detecting and handling completion IO errors is done individually
> -	 * for each case as different cleanup operations need to be performed
> -	 * on error.
> +	 * Success:  commit the COW or unwritten blocks if needed.
>  	 */
> -	if (ioend->io_type == XFS_IO_UNWRITTEN) {
> -		if (error)
> -			goto done;
> -		error = xfs_iomap_write_unwritten(ip, ioend->io_offset,
> -						  ioend->io_size);
> -	} else if (ioend->io_append_trans) {
> -		error = xfs_setfilesize_ioend(ioend, error);
> -	} else {
> -		ASSERT(!xfs_ioend_is_append(ioend) ||
> -		       ioend->io_type == XFS_IO_COW);
> +	switch (ioend->io_type) {
> +	case XFS_IO_COW:
> +		error = xfs_reflink_end_cow(ip, offset, size);
> +		break;
> +	case XFS_IO_UNWRITTEN:
> +		error = xfs_iomap_write_unwritten(ip, offset, size);
> +		break;
> +	default:
> +		ASSERT(!xfs_ioend_is_append(ioend) || ioend->io_append_trans);
> +		break;
>  	}
>  
>  done:
> +	if (ioend->io_append_trans)
> +		error = xfs_setfilesize_ioend(ioend, error);
>  	xfs_destroy_ioend(ioend, error);
>  }
>  
> -- 
> 2.11.0
> 
> --
> 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

  reply	other threads:[~2017-02-28  9:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28  0:49 [PATCH] xfs: fix and streamline error handling in xfs_end_io Christoph Hellwig
2017-02-28  5:34 ` Darrick J. Wong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-08 16:33 Christoph Hellwig
2017-03-08 17:56 ` Darrick J. Wong

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=20170228053420.GG5297@birch.djwong.org \
    --to=darrick.wong@oracle.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 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).