linux-kernel - Re: Boot time regression in 2.6.38 after initial wq merge

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4D640F67.3040109@versanet.de>
Date:	Tue, 22 Feb 2011 20:32:55 +0100
From:	"pantherchen@...sanet.de" <pantherchen@...sanet.de>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
CC:	Tejun Heo <tj@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Boot time regression in 2.6.38 after initial wq merge

On 02/22/2011 06:59 PM, Dmitry Torokhov wrote:
> On Tue, Feb 22, 2011 at 09:22:54AM -0800, Dmitry Torokhov wrote:
>> Just to confirm, if you revert commit
>>
>> 	8ee294cd9def0004887da7f44b80563493b0a097
>>
>> from 2.6.38-rc6, does this restore boot time?

Yes, it's booting fine with that commit reverted.

> And if that indeed fixes the issue I wonder if the reason for the stall
> is that we trip on flush_scheduled_work() somewhere. If you could stick
> dump_stack() into flush_scheduled_work() that might give us some clues.

I wasn't sure where to put the dump_stack() call, so I placed one before 
and one after the flush_workqueue() call.

Here's the part that turned up in dmesg: http://paste.ubuntu.com/570729/

Regards,

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