[PATCH 4.9 114/172] pmem: return EIO on read_pmem() failure

From: Greg Kroah-Hartman
Date: Mon Jul 03 2017 - 10:23:15 EST

4.9-stable review patch. If anyone has any objections, please let me know.


From: Stefan Hajnoczi <stefanha@xxxxxxxxxx>

[ Upstream commit d47d1d27fd6206c18806440f6ebddf51a806be4f ]

The read_pmem() function uses memcpy_mcsafe() on x86 where an EFAULT
error code indicates a failed read. Block I/O should use EIO to
indicate failure. Other pmem code paths (like bad blocks) already use
EIO so let's be consistent.

This fixes compatibility with consumers like btrfs that try to parse the
specific error code rather than treat all errors the same.

Reviewed-by: Jeff Moyer <jmoyer@xxxxxxxxxx>
Signed-off-by: Stefan Hajnoczi <stefanha@xxxxxxxxxx>
Signed-off-by: Dan Williams <dan.j.williams@xxxxxxxxx>
Signed-off-by: Sasha Levin <alexander.levin@xxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
drivers/nvdimm/pmem.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)

--- a/drivers/nvdimm/pmem.c
+++ b/drivers/nvdimm/pmem.c
@@ -87,7 +87,9 @@ static int read_pmem(struct page *page,

rc = memcpy_from_pmem(mem + off, pmem_addr, len);
- return rc;
+ if (rc)
+ return -EIO;
+ return 0;

static int pmem_do_bvec(struct pmem_device *pmem, struct page *page,