summaryrefslogtreecommitdiff
path: root/drivers/dma
diff options
context:
space:
mode:
authorDave Jiang <dave.jiang@intel.com>2013-11-06 19:50:09 +0400
committerDan Williams <dan.j.williams@intel.com>2013-11-14 23:04:41 +0400
commitac7d631f7d9f9e4e6116c4a72b6308067d0a2226 (patch)
tree4d0dd8fd5866c28d56151a013108838a8eea7d0b /drivers/dma
parent50137a7df982f3767fe0b3b0cd0b9cfaf09c2cd9 (diff)
downloadlinux-ac7d631f7d9f9e4e6116c4a72b6308067d0a2226.tar.xz
ioatdma: Fix bug in selftest after removal of DMA_MEMSET.
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. Cc: <stable@vger.kernel.org> Signed-off-by: Dave Jiang <dave.jiang@intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
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 a4798f0cc225..44786ad2a4cf 100644
--- a/drivers/dma/ioat/dma_v3.c
+++ b/drivers/dma/ioat/dma_v3.c
@@ -1376,6 +1376,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;