lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 29 Oct 2007 22:17:40 -0600 From: Robert Hancock <hancockr@...w.ca> To: linux-kernel <linux-kernel@...r.kernel.org>, ide <linux-ide@...r.kernel.org> Subject: sata_nv and dynamically changing DMA mask? In the sata_nv driver, when running in ADMA mode, we can do 64-bit DMA. However, when an ATAPI device like a DVD drive is connected, we can't use ADMA mode, and so we have to abide by the restrictions of a normal SFF ATA controller and can only do 32-bit DMA. We detect this and try to set the blk_queue_bounce_limit, blk_queue_segment_boundary and blk_queue_max_hw_segments to the values corresponding to a normal SFF controller. However, we have this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=351451 that their DVD drive doesn't work properly on a computer with 4GB of RAM unless they either disable ADMA (thus resulting in the DMA parameters being initialized to the SFF ones from the start) or pass mem=3000M to the kernel to keep the memory above the 4GB mark from being used. Thus I suspect that what we're trying to do with the DMA parameters is not taking. Question is: is setting blk_queue_bounce_limit enough to prevent addresses outside that mask from showing up, or does the device DMA mask also need to be updated? Is there anything wrong with just changing the DMA mask at runtime? Keep in mind, ATAPI and non-ATAPI devices can potentially be switched out on the port, so the mask might need to be updated at runtime.. -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from hancockr@...pamshaw.ca Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists