linux-kernel - Re: [BUGFIX] cpufreq: dont BUG

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: <20100113155905.GA1965@redhat.com>
Date:	Wed, 13 Jan 2010 10:59:06 -0500
From:	Dave Jones <davej@...hat.com>
To:	Thomas Renninger <trenn@...e.de>
Cc:	Wu Fengguang <fengguang.wu@...el.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [BUGFIX] cpufreq: dont BUG_ON uninitialized policy cpu

On Wed, Jan 13, 2010 at 01:42:36PM +0100, Thomas Renninger wrote:
 > On 01/13/2010 06:14 AM, Wu Fengguang wrote:
 > > Remove a BUG_ON which is always triggered here after commit 0b19a310eebb93:
 > The patch got dropped from -mm.
 > I hope it did not make it upstream yet, otherwise it should also
 > get dropped/reverted there without replacement.
 > There wasn't a real, only a theoretical issue.
 > Looking at it again, I now think it's not needed at all.
 
dropped from cpufreq.git

I'm still curious how we're calling cpufreq_update_policy with no policy set.
I suspect cpufreq_stats might be doing something wrong.

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