linux-kernel - Re: [BUG cpufreq] Invalid argument on writing to scaling

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:	Fri, 01 Aug 2014 14:47:53 +0200
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Prarit Bhargava <prarit@...hat.com>
Cc:	Fengguang Wu <fengguang.wu@...el.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	Aaron Lu <aaron.lu@...el.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [BUG cpufreq] Invalid argument on writing to scaling_governor

On Friday, August 01, 2014 06:46:51 AM Prarit Bhargava wrote:
> 
> On 08/01/2014 06:43 AM, Fengguang Wu wrote:
> > Hi Prarit,
> > 
> > I noticed that commit dbcbfe6aa0d61ae5e13cab43b30802482007c199 ("cpufreq: hold
> > policy->rwsem for duration of changing governors") will cause this problem:
> > 
> > root@...4 ~# echo performance > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
> > -bash: echo: write error: Invalid argument
> > 
> > root@...4 ~# cat /sys/devices/system/cpu/cpu3/cpufreq/scaling_available_governors
> > conservative userspace powersave ondemand performance
> > 
> 
> Rafael, this patch needs to be rejected based on my previous comments, most
> notably Saravana was able to reproduce the original problem.  I'm going to wait
> for his reproducer and see what I can do.

I've dropped it already.  At least as far as I can say it shouldn't be there in
my linux-next branch any more.  Can you double check, please?

Rafael

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