linux-kernel - Re: [2.6.33-rc5] Weird deadlock when shutting down

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: <1266751349.10419.2.camel@jlt3.sipsolutions.net>
Date:	Sun, 21 Feb 2010 12:22:29 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	Xiaotian Feng <xtfeng@...il.com>
Cc:	Américo Wang <xiyou.wangcong@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [2.6.33-rc5] Weird deadlock when shutting down

On Sun, 2010-02-21 at 12:14 +0100, Johannes Berg wrote:

>         printk("got cpu\n");
>         for_each_online_cpu(i) {
>                 sm_work = per_cpu_ptr(stop_machine_work, i);
>                 INIT_WORK(sm_work, stop_cpu);
>                 queue_work_on(i, stop_machine_wq, sm_work);
>         }
>         /* This will release the thread on our CPU. */
>         put_cpu();
>         printk("put cpu\n");

As odd as that may be, it hangs in put_cpu() here.

johannes

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