linux-kernel - Re: BUG in drivers/dma/ioat/dma

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 01 Jul 2010 07:21:04 +0100
From:	David Woodhouse <David.Woodhouse@...el.com>
To:	"Williams, Dan J" <dan.j.williams@...el.com>
Cc:	Chris Li <lkml@...isli.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: BUG in drivers/dma/ioat/dma_v2.c:314

On Wed, 2010-06-30 at 22:44 +0100, Williams, Dan J wrote:
> I don't see a way around this beyond blacklisting this (platform, vt-d 
> setting, driver) combination.  Is there a quirk infrastructure for this 
> sort of problem?

Yeah, kind of. If the IOAT PCI device _always_ has its own IOMMU, we
could have a quirk for it which says it must _never_ be matched by a
catch-all IOMMU. That would probably solve it?

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@...el.com                              Intel Corporation

--
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/