summaryrefslogtreecommitdiff
path: root/drivers/dma
diff options
context:
space:
mode:
authorDave Jiang <dave.jiang@intel.com>2013-11-06 19:50:09 +0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-12-04 23:05:36 +0400
commitb9c4b04c214848774fbbee4d946aa39ecb8f1010 (patch)
tree0ebeeb7b1f7501d075e2773aa7ea659add06bd85 /drivers/dma
parent9afdbf0a4e3d7ea4030de51ca4b73de5c18386ec (diff)
downloadlinux-b9c4b04c214848774fbbee4d946aa39ecb8f1010.tar.xz
ioatdma: Fix bug in selftest after removal of DMA_MEMSET.
commit ac7d631f7d9f9e4e6116c4a72b6308067d0a2226 upstream. Commit 48a9db4 (3.11) removed the memset op in the xor selftest for ioatdma. The issue is that with the removal of that op, it never replaced the memset with a CPU memset. The memory being operated on is expected to be zeroes but was not. This is causing the xor selftest to fail. Signed-off-by: Dave Jiang <dave.jiang@intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/dma')
-rw-r--r--drivers/dma/ioat/dma_v3.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/dma/ioat/dma_v3.c b/drivers/dma/ioat/dma_v3.c
index d8ececaf1b57..fa32d9f8166a 100644
--- a/drivers/dma/ioat/dma_v3.c
+++ b/drivers/dma/ioat/dma_v3.c
@@ -1545,6 +1545,8 @@ static int ioat_xor_val_self_test(struct ioatdma_device *device)
goto free_resources;
}
+ memset(page_address(dest), 0, PAGE_SIZE);
+
/* test for non-zero parity sum */
op = IOAT_OP_XOR_VAL;