linux-kernel - Re: [PATCH] e1000e: prevent concurrent access to NVRAM

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:	Thu, 2 Oct 2008 17:19:06 -0700
From:	"Jesse Brandeburg" <jesse.brandeburg@...il.com>
To:	"Thomas Gleixner" <tglx@...utronix.de>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Olaf Kirch" <okir@...e.de>, "Jiri Kosina" <jkosina@...e.cz>,
	"Jesse Brandeburg" <jesse.brandeburg@...el.com>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-netdev@...r.kernel.org, kkeil@...e.de, agospoda@...hat.com,
	arjan@...ux.intel.com, david.graham@...el.com,
	bruce.w.allan@...el.com, john.ronciak@...el.com,
	chris.jones@...onical.com, tim.gardner@...el.com,
	airlied@...il.com, "Ingo Molnar" <mingo@...e.hu>
Subject: Re: [PATCH] e1000e: prevent concurrent access to NVRAM

On Thu, Oct 2, 2008 at 4:42 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
> The confirmed bugs where the nvram acquire code was called
> concurrently are still in your tree and the prevention patch along
> with the resulting bugfixes are stuck in some obscure intel QA
> process.
>
> Please apply at least the bug prevention patch below.

This is the same patch I posted 7 minutes ago, except that this patch
without the e1000e changes applied before it will cause all sorts of
WARN's to be printed during normal operation.  If at all possible I
think they should stay together as a group to prevent un-necessary
noise in the logs.
--
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/