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:	Fri, 7 Mar 2014 23:39:29 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Dave Jones <davej@...hat.com>
Cc:	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Fengguang Wu <fengguang.wu@...el.com>,
	Ingo Molnar <mingo@...nel.org>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Paolo Bonzini <pbonzini@...hat.com>
Subject: Re: [qemu64,+smep,+smap] WARNING: CPU: 1 PID: 0 at
 arch/x86/kernel/cpu/amd.c:220 init_amd()

On Fri, Mar 07, 2014 at 05:27:43PM -0500, Dave Jones wrote:
> When I wrote it 10 years or so back it made more sense than it
> probably does now, so I'd be ok with just dropping it all too tbh.
> Machines of that vintage probably have bigger problems now anyway.

Yeah.

> I don't recall seeing a report of the taint flag being set ever in
> a Red Hat bug report, but we've seen countless problems from machines
> of that era with dying ram or motherboard capacitors or..

Right, this should be a sufficient indicator that those machines won't
be running modern kernels anymore :-)

Oh, and besides, this really frees up that taint bit TAINT_UNSAFE_SMP
for the forcepae thing. Let me cook up a patch - it looks like 3.14
will be the release where we're getting rid of old platforms - look at
tip/x86/nuke-platforms. :-)

> I still have NexGen docs somewhere ;)

Uuuh, more than ancient, make sure to hold on to those :-)

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ