From: Filipe Manana <fdman...@suse.com>
Hi Chris,
Please consider the following fix for an upcoming 4.5 release candidate.
It fixes a problem where if the bio for a direct IO request fails, we end
reporting success to userspace. For example, for a direct IO write of 64K,
if the block layer notifies us that an IO error happened with our bio, we
end up returning the value 64K to user space instead of -EIO, making the
application think that its write request succeeded.
This is reproducible with the new generic test cases in xfstests: 271,
272, 276 and 278 (which use dm's error target to simulate IO errors).
Thanks.
The following changes since commit bc4ef7592f657ae81b017207a1098817126ad4cb:
btrfs: properly set the termination value of ctx->pos in readdir (2016-02-11
07:01:59 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/fdmanana/linux.git for-chris-4.5
for you to fetch changes up to 1636d1d77ef4e01e57f706a4cae3371463896136:
Btrfs: fix direct IO requests not reporting IO error to user space
(2016-02-16 03:41:26 +0000)
----------------------------------------------------------------
Filipe Manana (1):
Btrfs: fix direct IO requests not reporting IO error to user space
fs/btrfs/inode.c | 2 ++
1 file changed, 2 insertions(+)
--
2.7.0.rc3
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
