linux-kernel - Re: SPAM: Re: _cpu_down deadlock [was Re: 2.6.19-rc1-mm1]

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, 12 Oct 2006 01:04:06 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Neil Brown <neilb@...e.de>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	Pavel Machek <pavel@....cz>, "Rafael J. Wysocki" <rjw@...k.pl>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	rusty@...tcorp.com.au
Subject: Re: SPAM: Re: _cpu_down deadlock [was Re: 2.6.19-rc1-mm1]

On Thu, 12 Oct 2006 17:53:11 +1000
Neil Brown <neilb@...e.de> wrote:

> I think I'm in favour of the following. 

Would be simpler to take cpu_add_remove_lock in
[un]register_cpu_notifier().  I actually thought I'd done that to fix this
bug but must have forgotten or lost the patch :(

We can then convert all the notifier chains in there to raw_*.

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