linux-kernel - Re: [ANNOUNCE] Merkey's Kernel Debugger

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: <1218122251.8625.40.camel@twins>
Date:	Thu, 07 Aug 2008 17:17:31 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	jmerkey@...fmountaingroup.com
Cc:	Andi Kleen <andi@...stfloor.org>,
	Jason Wessel <jason.wessel@...driver.com>,
	Nick Piggin <nickpiggin@...oo.com.au>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Stefan Richter <stefanr@...6.in-berlin.de>,
	Josh Boyer <jwboyer@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE] Merkey's Kernel Debugger

On Thu, 2008-08-07 at 06:45 -0600, jmerkey@...fmountaingroup.com wrote:

> Also, whoever wrote "/Documentation/volatiles_are_evil" must not have
> worked with the busted-ass GNU compiler that optimizes away global
> variables and busts SMP dependent code.  I am not going to remove the
> volatile declarations needed for SMP coordination in the debugger since
> the code breaks when removed.  GCC will cause massive breakage of SMP code
> if you do not declare certain variables as volatile.

Even with proper barrier() usage?


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