linux-kernel - Re: [GIT PULL] x86 fixes

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]

Message-ID: <CA+55aFz2b_HYRuATpquNEo1yD=iWLJmCQAJ2pxYcsePjpY+CiQ@mail.gmail.com>
Date:	Sat, 12 Oct 2013 12:41:32 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Matthew Garrett <matthew.garrett@...ula.com>
Cc:	Ingo Molnar <mingo@...nel.org>, Peter Anvin <hpa@...or.com>,
	Avi Kivity <avi@...hat.com>, Len Brown <len.brown@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] x86 fixes

On Sat, Oct 12, 2013 at 12:28 PM, Matthew Garrett
<matthew.garrett@...ula.com> wrote:
>
> The most likely cause of the problem that we're seeing here is that we're leaving the hardware in a state that isn't compatible with assumptions made by Dell's SMM code. We've certainly seen that some previous Dell machines have made incorrect assumptions about VT-d, which probably means that we should be destroying that state before reboot. David Woodhouse had been looking into that - I don't know whether we ever actually merged anything to do so.

I have access to one of the affected Dell systems, so I'm willing to
try patches..

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