The patch titled
atl1: fix 4G memory corruption bug
has been removed from the -mm tree. Its filename was
atl1-fix-4g-memory-corruption-bug.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: atl1: fix 4G memory corruption bug
From: Alexey Dobriyan <adobriyan@xxxxxxxxx>
When using 4+ GB RAM and SWIOTLB is active, the driver corrupts memory by
writing an skb after the relevant DMA page has been unmapped. Although
this doesn't happen when *not* using bounce buffers, clearing the pointer
to the DMA page after unmapping it fixes the problem.
Signed-off-by: Jay Cliburn <jacliburn@xxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/net/atlx/atl1.c | 1 +
1 file changed, 1 insertion(+)
diff -puN drivers/net/atlx/atl1.c~atl1-fix-4g-memory-corruption-bug drivers/net/atlx/atl1.c
--- a/drivers/net/atlx/atl1.c~atl1-fix-4g-memory-corruption-bug
+++ a/drivers/net/atlx/atl1.c
@@ -2023,6 +2023,7 @@ rrd_ok:
/* Good Receive */
pci_unmap_page(adapter->pdev, buffer_info->dma,
buffer_info->length, PCI_DMA_FROMDEVICE);
+ buffer_info->dma = 0;
skb = buffer_info->skb;
length = le16_to_cpu(rrd->xsz.xsum_sz.pkt_size);
_
Patches currently in -mm which might be from adobriyan@xxxxxxxxx are
edd-fix-incorrect-return-of-1-from-module_init.patch
linux-next.patch
cifs-switch-to-seq_files.patch
isdn-divas-fix-proc-creation.patch
mpt-remove-unused-struct-mpt_proc_entry_t.patch
proc-calculate-the-correct-proc-pid-link-count.patch
proc-calculate-the-correct-proc-pid-link-count-cleanup.patch
move-proc_kmsg_operations-to-fs-proc-internalh.patch
sysctl-allow-override-of-proc-sys-net-with-cap_net_admin.patch
proc-use-non-racy-method-for-proc-page_owner-creation-page_owner.patch
likely_prof-changed-to-use-proc_create.patch
proc-remove-proc_root-from-drivers-likelyprof.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
