linux-kernel - Re: [crash] kernel BUG at drivers/cpufreq/cpufreq.c:1060!

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] [day] [month] [year] [list]

Message-ID: <20071213175038.GD28148@redhat.com>
Date:	Thu, 13 Dec 2007 12:50:38 -0500
From:	Dave Jones <davej@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org, "Rafael J. Wysocki" <rjw@...k.pl>,
	venkatesh.pallipadi@...el.com
Subject: Re: [crash] kernel BUG at drivers/cpufreq/cpufreq.c:1060!

On Thu, Dec 13, 2007 at 11:17:11AM +0100, Ingo Molnar wrote:
 > 
 > * Dave Jones <davej@...hat.com> wrote:
 > 
 > >  > It _looks_ like we're leaking a refcount on that lock, but I don't 
 > >  > see where.  It's a shame you can't reproduce this easily, as 
 > >  > cpufreq.debug=7 would give us more clues. (And 
 > >  > CONFIG_CPUFREQ_DEBUG=y)
 > > 
 > > So we're missing some unlocks in some error paths. It's feasible you 
 > > hit one of those. This patch should be the fix for that.
 > 
 > since it's not really reproducible (i failed to get it since then), how 
 > about you push your fix upstream (it's an obviously correct fix), we 
 > consider this regression fixed and i'll re-notify you if there's still 
 > any problem left. It's not like there's any escape from make randconfig 
 > bootup test coverage in the long run ;-)

Yeah, will push it to Linus today.

	Dave

-- 
http://www.codemonkey.org.uk
--
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/