linux-kernel - Re: hrtimer deadlock caused by nohz

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]

Date:	Tue, 7 Oct 2014 19:42:47 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Dave Jones <davej@...hat.com>
cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Peter Zijlstra <peterz@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: hrtimer deadlock caused by nohz_full

On Tue, 7 Oct 2014, Dave Jones wrote:

> On Tue, Oct 07, 2014 at 05:30:27PM +0200, Frederic Weisbecker wrote:
> 
>  > >  > Right, this patchset fixes it: "[PATCH 0/8] nohz: Fix nohz kick irq work on tick v3"
>  > >  > 
>  > >  > I was about to make the pull request, the branch is acked by peterz.
>  > >  > Would you like to pull it? It's all merge window material.
>  > >  > 
>  > >  > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
>  > >  > 	nohz/fixes-v3
>  > > 
>  > > I'm now hitting this with such regularity that it's preventing me from
>  > > tracking down other bugs.  Can we get this merged soon please ?
>  > 
>  > I asked Thomas to pull but he probably missed it. So I did a formal pull request
>  > to Ingo a few days later but he told me that the pull request was made too late
>  > as the merge window was too close. I told him it fixes annoying bugs but that was on IRC
>  > so this probably got lost.

Aarg. Lemme get this done.

Thanks,

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