linux-kernel - Re: [3.2-rc3] 100% CPU usage while in del_timer_sync from iwl3945_rs_free

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]

Date:	Thu, 1 Dec 2011 10:09:45 +0800
From:	Yong Zhang <yong.zhang0@...il.com>
To:	Michal Hocko <mhocko@...e.cz>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Stanislaw Gruszka <sgruszka@...hat.com>,
	"John W. Linville" <linville@...driver.com>,
	linux-wireless@...r.kernel.org
Subject: Re: [3.2-rc3] 100% CPU usage while in del_timer_sync from
 iwl3945_rs_free_sta

On Tue, Nov 29, 2011 at 11:07:27AM +0100, Michal Hocko wrote:
> Looks we are stuck in lock_timer_base loop. I am not familiar with the
> code but either base is NULL or we are racing with timer->base changes.
> I guess that the first one sounds more probable. The timer in question
> is &rs_sta->rate_scale_flush.

FYI

If you could apply below commits in -tip/core/debugobjects
dc4218b timer: Use debugobjects to catch deletion of uninitialized timers
fb16b8c timer: Setup uninitialized timer with a stub callback
b84d435 debugobjects: Extend to assert that an object is initialized
feac18d debugobjects: Be smarter about static objects

and enable DEBUG_OBJECTS_TIMERS, maybe you can catch something easily.

Thanks,
Yong
--
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/