| 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: Tue, 09 Sep 2008 20:37:28 -0700 (PDT) From: David Miller <davem@...emloft.net> To: zaitcev@...hat.com Cc: jdmason@...zu.us, muli@...ibm.com, linux-kernel@...r.kernel.org Subject: Re: Calgary and bad_dma_address From: Pete Zaitcev <zaitcev@...hat.com> Date: Tue, 9 Sep 2008 21:19:41 -0600 > I was reading arch/x86/kernel/pci-calgary_64.c today, and noticed that > apparently nothing prevents iommu_area_alloc from returning a zero. > But bad_dma_address is zero too. Doesn't it concern anyone? > If the first allocation asks for a page-aligned buffer to be mapped, > a spurious bad address will result, if I understand this right. Won't the device range reserves done by calls of calgary_reserve_mem_region() take care of this? -- 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