linux-kernel - Re: [BUG] 2.6.29.1 debugobjects warning

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:	Mon, 27 Apr 2009 13:30:13 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	gregkh@...e.de, linux-kernel@...r.kernel.org,
	cpufreq@...r.kernel.org
Subject: Re: [BUG] 2.6.29.1 debugobjects warning

On Fri, 24 Apr 2009, Ingo Molnar wrote:
> 
> * Andrew Morton <akpm@...ux-foundation.org> wrote:
> 
> > On Thu, 23 Apr 2009 10:00:02 -0400
> > Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> wrote:
> > 
> > > ODEBUG: init active object type: timer_list
> 
> > It seems to be complaining that cpufreq_governor_dbs() is running 
> > init_timer() against a timer which has already been initialised 
> > once.
> 
> Not just already initialized - but also active. There's these states 
> for an object:
> 
>         ODEBUG_STATE_NONE,
>         ODEBUG_STATE_INIT,
>         ODEBUG_STATE_INACTIVE,
>         ODEBUG_STATE_ACTIVE,
>         ODEBUG_STATE_DESTROYED,
> 
> So the 'init active object type' warning above suggests that an 
> init_timer() has been done on an already running timer. If true then 
> that is a bad bug - can corrupt timer state, etc.
> 
> Thomas, do you agree?

Yes, that kind of bug makes the timer wheel explode later on due to
list corruption.

Thanks,

	tglx

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