linux-kernel - Re: [PATCH 00/19] Fix Intel IOMMU breakage in kdump kernel

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] [day] [month] [year] [list]

Date:	Thu, 25 Jun 2015 09:06:40 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	"Li, ZhenHua" <zhen-hual@...com>
Cc:	Joerg Roedel <jroedel@...e.de>, Joerg Roedel <joro@...tes.org>,
	iommu@...ts.linux-foundation.org, bhe@...hat.com,
	ddutile@...hat.com, alex.williamson@...hat.com, dyoung@...hat.com,
	linux-kernel@...r.kernel.org, jroedel@...tes.org
Subject: Re: [PATCH 00/19] Fix Intel IOMMU breakage in kdump kernel

On Thu, 2015-06-25 at 14:35 +0800, Li, ZhenHua wrote:
> Hi David,
> It is a bad idea to check the DMI match on "HP". Though I have not see
> any similar problems on other systems, I believe there are. Also not
> all HP systems have such problem.

Yeah, the HP suggestion was a little tongue-in-cheek. Although it does
seem to be HP who is the main offender in this area — both the BIOS
"value subtract" and the habit of doing utterly insane things with the
IOMMU.

> I agree with a blacklist for devices.

Do you have a list of the problematic ones? I think a blacklist *and*
an option to enable it for all devices might be the best solution.

-- 
dwmw2


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