linux-kernel - Re: Linux 2.6.35-rc3

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]

Date:	Sat, 12 Jun 2010 09:34:21 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...hat.com>, cpufreq@...r.kernel.org,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: Linux 2.6.35-rc3

On Sat, 12 Jun 2010 11:59:03 +0200 Borislav Petkov <bp@...en8.de> wrote:

> From: Linus Torvalds <torvalds@...ux-foundation.org>
> Date: Fri, Jun 11, 2010 at 08:01:22PM -0700
> 
> > So give it a good testing.
> 
> This one still triggers the warning below. Now there's supposedly a fix
> at least at http://www.spinics.net/lists/cpufreq/msg01631.html
> 
> Can we get it in anytime soon?
> 
> Thanks.
> 
> [   13.120063] BUG: using smp_processor_id() in preemptible [00000000] code: cpufreq-set/1757
> [   13.120310] caller is nr_iowait_cpu+0x1a/0x30
> [   13.120495] Pid: 1757, comm: cpufreq-set Not tainted 2.6.35-rc3 #2
> [   13.120636] Call Trace:
> [   13.120777]  [<ffffffff811ab552>] debug_smp_processor_id+0xc2/0xdc
> [   13.120919]  [<ffffffff81028e1e>] nr_iowait_cpu+0x1a/0x30
> [   13.120921]  [<ffffffff81062a22>] update_ts_time_stats+0x3c/0x77
> [   13.120925]  [<ffffffff8105e390>] ? ktime_get+0x65/0xbe
> [   13.120927]  [<ffffffff81062c03>] get_cpu_idle_time_us+0x49/0x68
> [   13.120932]  [<ffffffffa0047d20>] cpufreq_governor_dbs+0xeb/0x40f [cpufreq_ondemand]
> [   13.120936]  [<ffffffff81348094>] __cpufreq_governor+0x16b/0x1c6
> [   13.120941]  [<ffffffff8134937a>] __cpufreq_set_policy+0x119/0x156
> [   13.120943]  [<ffffffff813497e6>] store_scaling_governor+0x195/0x1cf
> [   13.120946]  [<ffffffff8134a033>] ? handle_update+0x0/0x13
> [   13.120949]  [<ffffffff8134923f>] store+0x5e/0x80
> [   13.120952]  [<ffffffff811320ac>] sysfs_write_file+0x108/0x144
> [   13.120955]  [<ffffffff810dd3d2>] vfs_write+0xb2/0x153
> [   13.120957]  [<ffffffff810dd536>] sys_write+0x4a/0x71
> [   13.120960]  [<ffffffff8100221b>] system_call_fastpath+0x16/0x1b

Last I heard, Arjan was looking into this.
--
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/