linux-kernel - Re: Buggy IPI and MTRR code on low memory

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.1.10.0901281221450.25359@gandalf.stny.rr.com>
Date:	Wed, 28 Jan 2009 12:24:48 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Peter Zijlstra <peterz@...radead.org>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Rusty Russell <rusty@...tcorp.com.au>, jens.axboe@...cle.com
Subject: Re: Buggy IPI and MTRR code on low memory


On Wed, 28 Jan 2009, Peter Zijlstra wrote:
> ---
> Subject: x86: fix potential deadlock in set_mtrr()
> From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
> Date: Wed Jan 28 17:17:32 CET 2009
> 
> smp_call_function() can fall-back to waiting on completion in case of
> low memory (GFP_ATOMIC). set_mtrr() relies on the async behaviour of !wait.
> 
> This would deadlock.
> 
> Fix this by providing per-cpu csd's and using __smp_call_function_single().

I applied the patch but it still locked up in the testing NMI 
watchdog code. Not saying your patch is at fault, because we never made it 
to your code. This is probably not an issue, since if we have low memory 
at bootup, we have much bigger problems to deal with.

I'll have skip the NMI test and see if it locks up any place else.

-- Steve


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