linux-kernel - Re: [ANNOUNCE] 3.14.23-rt20

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: <CAKudYbNhjdNmw27tMz261p+6q4OStBp2zUoBsgtJdQGcJ9fkKw@mail.gmail.com>
Date:	Wed, 5 Nov 2014 15:35:51 +0000
From:	Harry van Haaren <harryhaaren@...il.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Juerg Haefliger <juergh@...il.com>,
	Mike Galbraith <umgwanakikbuti@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-rt-users <linux-rt-users@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Carsten Emde <C.Emde@...dl.org>,
	John Kacur <jkacur@...hat.com>,
	Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
	Clark Williams <williams@...hat.com>
Subject: Re: [ANNOUNCE] 3.14.23-rt20

On Wed, 5 Nov 2014 14:50:41 +0100 Juerg Haefliger <juergh@...il.com> wrote:
> The cpufreq code does nested down_read_trylocks and only the first one succeeds:
>drivers/cpufreq/cpufreq.c:
>store
>  down_read_trylock(cpufreq_rwsem)  <- succeeds
>  store_scaling_governor
>    cpufreq_get_policy
>      cpufreq_cpu_get
>        down_read_trylock(cpufreq_rwsem)  <-- fails

On a related note: I think this patch/issue may be the cause of the
-rt CPU frequency scaling bug I reported a couple of months ago.
http://comments.gmane.org/gmane.linux.rt.user/12472

I'm currently using the performance governor by default as a
workaround; thanks to JackWinter for packaging in the ArchAudio repos.

Cheers, -Harry

-- 

http://www.openavproductions.com
--
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/