linux-kernel - Re: Possible regression due to "tick: broadcast: Prevent livelock from event handler"

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: <5596A2D4.4080103@arm.com>
Date:	Fri, 03 Jul 2015 15:57:24 +0100
From:	Sudeep Holla <sudeep.holla@....com>
To:	Thomas Gleixner <tglx@...utronix.de>
CC:	Sudeep Holla <sudeep.holla@....com>,
	Wolfram Sang <wsa@...-dreams.de>,
	Geert Uytterhoeven <geert+renesas@...der.be>,
	Kevin Hilman <khilman@...nel.org>,
	Magnus Damm <magnus.damm@...il.com>,
	"linux-sh@...r.kernel.org" <linux-sh@...r.kernel.org>,
	Tyler Baker <tyler.baker@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Simon Horman <horms@...ge.net.au>,
	Borislav Petkov <bp@...en8.de>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: Possible regression due to "tick: broadcast: Prevent livelock
 from event handler"



On 03/07/15 15:54, Thomas Gleixner wrote:
> On Fri, 3 Jul 2015, Sudeep Holla wrote:
>> On 03/07/15 15:37, Wolfram Sang wrote:
>>>
>>>> So this is a single core machine and uses the em_sti timer w/o the
>>>> broadcast nonsense. In Simons case it looks like em_sti is used as
>>>> broadcast device.
>>>
>>> We use the same board. Just my kernel has SMP=n.
>>>
>>
>> If it's UP build, then GENERIC_CLOCKEVENTS_BROADCAST is disabled. You
>> may be hitting the issue I reported[1] and is still under discussion.
>
> Nope. The UP version uses a non affected timer.
>

Ah OK, sorry for the noise then.

Regards,
Sudeep
--
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/