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: Wed, 23 Jul 2014 17:10:40 +0200 From: Joerg Roedel <joro@...tes.org> To: Greg Edwards <gedwards@....com> Cc: David Woodhouse <dwmw2@...radead.org>, iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] iommu/vt-d: fix race between free_irte() and get_irte() On Wed, Jul 23, 2014 at 08:49:17AM -0600, Greg Edwards wrote: > On Wed, Jul 23, 2014 at 04:40:24PM +0200, Joerg Roedel wrote: > > On Tue, Jul 22, 2014 at 08:27:19AM -0600, Greg Edwards wrote: > >> get_irte() can race with free_irte() and dereference a NULL iommu > >> pointer. > > > > Have you seen any real occurance of this race? Get_irte is called in the > > set_affinity path, how can that race with the irq being freed? > > Yes, that's how we hit it. A process was setting the CPU affinity while > QEMU was releasing the IRQ. We have a CI stress test that turned this > up. Can you update the commit message with the details of how this race can be triggered, ideally with a stack-trace of a real crash you triggered because of this issue? Thanks, Joerg -- 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