linux-kernel - Re: next-20130206 cpufreq

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: <1729273.hgXged98n0@vostro.rjw.lan>
Date:	Thu, 07 Feb 2013 02:12:17 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Valdis.Kletnieks@...edu
Cc:	linux-kernel@...r.kernel.org, cpufreq@...r.kernel.org,
	linux-pm@...r.kernel.org, Viresh Kumar <viresh.kumar@...aro.org>
Subject: Re: next-20130206 cpufreq - WARN in sysfs_add_one

On Wednesday, February 06, 2013 07:55:58 PM Valdis.Kletnieks@...edu wrote:
> On Wed, 06 Feb 2013 22:24:39 +0100, "Rafael J. Wysocki" said:
> > On Wednesday, February 06, 2013 12:44:35 PM Valdis Kletnieks wrote:
> > > Seen in dmesg.  next-20130128 was OK. Haven't done a bisect, but can
> > > do so if the offender isn't obvious...
> >
> > I suppose this is 73bf0fc "cpufreq: Don't remove sysfs link for policy->cpu".
> >
> > Can you test the linux-pm.git/pm-cpufreq branch alone, please, and see
> > if that's this one (top-most commit)?
> 
> Color me mystified.  I can't find that commit by either number or
> the description:
> 
> [/usr/src/linux-next] git log | egrep -i 'cpufreq.*remove.*link'
> [/usr/src/linux-next] git log | grep -i 73bf0fc
> [/usr/src/linux-next]
> 
> Was that a very recent commit that may have gotten pushed too late
> for the next-20130206 merge?

Well, sorry, next-20130206 didn't include that commit.

Can you please test the linux-pm.git/pm-cpufreq branch, then?

Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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/