linux-kernel - Re: RCU detected CPU 0 stall after panic on sparc64

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: <20091214231523.GH6679@linux.vnet.ibm.com>
Date:	Mon, 14 Dec 2009 15:15:23 -0800
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	David Miller <davem@...emloft.net>
Cc:	mroos@...ux.ee, linux-kernel@...r.kernel.org,
	sparclinux@...r.kernel.org
Subject: Re: RCU detected CPU 0 stall after panic on sparc64

On Mon, Dec 14, 2009 at 01:02:01PM -0800, David Miller wrote:
> From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
> Date: Mon, 14 Dec 2009 12:25:56 -0800
> 
> > Hmmm...  At first glance, it looks like RCU should put a notifier onto
> > the panic_notifier_list to disable this check.  Or is there some global
> > variable that I can check?
> 
> Probably the notifier works just fine.

OK, will take that approach.

							Thanx, Paul
--
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/