Messages in this thread | | | Date | Mon, 12 Mar 2007 10:56:24 -0400 | From | Jeff Garzik <> | Subject | Re: data corruption with nvidia chipsets and IDE/SATA drives (k8 cpu errata needed?) |
| |
Andi Kleen wrote: > in Linux. Apparently in some cases sata_nv does DMA on an already freed and then > reused mapping.
Any data or additional info on that? Did you discover this by tracking the DMA API software routines, or something lower level (like a bus analyzer)?
libata handles all the DMA allocation and mapping and cleanup for sata_nv, so any software problem would affect the whole of libata.
But it's possible that the nForce SATA chip has DMA padding needs that are different from those provided by libata-core (grep for "pad"), which could create a situation where the hardware continues DMA'ing past the end of the DMA area.
Jeff
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |