From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: linux-fsdevel@vger.kernel.org
Cc: linux-block@vger.kernel.org, linux-xfs@vger.kernel.org,
axboe@kernel.dk, ak@linux.intel.com,
Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: [PATCH 2/2] xfs: remove assert to check bytes returned
Date: Mon, 29 Jan 2018 08:57:41 -0600 [thread overview]
Message-ID: <20180129145741.29486-2-rgoldwyn@suse.de> (raw)
In-Reply-To: <20180129145741.29486-1-rgoldwyn@suse.de>
From: Goldwyn Rodrigues <rgoldwyn@suse.com>
Since we can return less than count in case of partial direct
writes, remove the ASSERT.
Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
Acked-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
---
fs/xfs/xfs_file.c | 6 ------
1 file changed, 6 deletions(-)
diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
index 8601275cc5e6..8fc4dbf66910 100644
--- a/fs/xfs/xfs_file.c
+++ b/fs/xfs/xfs_file.c
@@ -590,12 +590,6 @@ xfs_file_dio_aio_write(
ret = iomap_dio_rw(iocb, from, &xfs_iomap_ops, xfs_dio_write_end_io);
out:
xfs_iunlock(ip, iolock);
-
- /*
- * No fallback to buffered IO on errors for XFS, direct IO will either
- * complete fully or fail.
- */
- ASSERT(ret < 0 || ret == count);
return ret;
}
--
2.16.1
next prev parent reply other threads:[~2018-01-29 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 14:57 [PATCH v6 1/2] Return bytes transferred for partial direct I/O Goldwyn Rodrigues
2018-01-29 14:57 ` Goldwyn Rodrigues [this message]
2018-01-29 18:50 ` [PATCH 2/2] xfs: remove assert to check bytes returned Jens Axboe
2018-01-29 19:04 ` [PATCH v6 1/2] Return bytes transferred for partial direct I/O Randy Dunlap
2018-01-30 17:31 ` Goldwyn Rodrigues
-- strict thread matches above, loose matches on Subject: below --
2018-01-19 0:57 [PATCH v5 " Goldwyn Rodrigues
2018-01-19 0:57 ` [PATCH 2/2] xfs: remove assert to check bytes returned Goldwyn Rodrigues
2018-01-19 3:57 ` Dave Chinner
2018-01-19 4:23 ` Raphael Carvalho
2018-01-19 4:51 ` 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=20180129145741.29486-2-rgoldwyn@suse.de \
--to=rgoldwyn@suse.de \
--cc=ak@linux.intel.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=rgoldwyn@suse.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 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).