linux-kernel - Re: [PATCH] change init_gdt to update the gdt via write

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]

Message-ID: <20080815165821.GA18777@elte.hu>
Date:	Fri, 15 Aug 2008 18:58:21 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Alex Nixon <alex.nixon@...rix.com>
Cc:	Jeremy Fitzhardinge <Jeremy.Fitzhardinge@...rix.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] change init_gdt to update the gdt via write_gdt,
	rather than a direct write.


* Alex Nixon <alex.nixon@...rix.com> wrote:

> From: Alex Nixon <alex.nixon@...rix.com>
> Date: Fri, 15 Aug 2008 11:21:56 +0100
> Subject: [PATCH] change init_gdt to update the gdt via write_gdt, rather than a direct write.
> 
> By writing directly, a memory access violation can occur whilst 
> hotplugging a CPU if the entry was previously marked read-only.

applied to tip/x86/urgent - thanks Alex.

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