linux-kernel - Re: tip/master broken with x2apic and kexec

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: <4C3C0A73.1090602@zytor.com>
Date:	Mon, 12 Jul 2010 23:40:51 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: tip/master broken with x2apic and kexec

On 07/12/2010 08:29 PM, Yinghai Lu wrote:
>
> offending patch is
>
> commit 83a7a2ad2a9173dcabc05df0f01d1d85b7ba1c2c
> Author: H. Peter Anvin<hpa@...ux.intel.com>
> Date:   Thu Jun 10 00:10:43 2010 +0000
>
>      x86, alternatives: Use 16-bit numbers for cpufeature index
>
>      We already have cpufeature indicies above 255, so use a 16-bit number
>      for the alternatives index.  This consumes a padding field and so
>      doesn't add any size, but it means that abusing the padding field to
>      create assembly errors on overflow no longer works.  We can retain the
>      test simply by redirecting it to the .discard section, however.
>
>      [ v3: updated to include open-coded locations ]
>
>      Signed-off-by: H. Peter Anvin<hpa@...ux.intel.com>
>      LKML-Reference:<tip-f88731e3068f9d1392ba71cc9f50f035d26a0d4f@....kernel.org>
>      Signed-off-by: H. Peter Anvin<hpa@...or.com>
>

Oh, good grief, what the hell is wrong with it this time...

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