linux-kernel - Re: [PATCH 1/3] slqb: Do not use DEFINE_PER

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: <1253577261.7103.169.camel@pasglop>
Date:	Tue, 22 Sep 2009 09:54:21 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Mel Gorman <mel@....ul.ie>
Cc:	Tejun Heo <tj@...nel.org>, Sachin Sant <sachinp@...ibm.com>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Nick Piggin <npiggin@...e.de>,
	Christoph Lameter <cl@...ux-foundation.org>,
	heiko.carstens@...ibm.com, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 1/3] slqb: Do not use DEFINE_PER_CPU for per-node data

On Mon, 2009-09-21 at 14:57 +0100, Mel Gorman wrote:
> Sachin should be enjoying his holiday and I'm hogging his machine at
> the
> moment.  However, I can report that with this patch applied as well as
> the
> remote-free patch that the machine locks up after a random amount of
> time
> has passed and doesn't respond to sysrq. Setting
> CONFIG_RCU_CPU_STALL_DETECTOR=y didn't help throw up an error. Will
> enable a few other debug options related to stall detection and see
> does
> it pop out.

You can also throw it into xmon (provided you have it enabled) using the
"dump restart" command from the HMC. This does the equivalent of an NMI.

Cheers,
Ben.



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