From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org ([198.145.29.99]:49260 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726500AbeLNHSa (ORCPT ); Fri, 14 Dec 2018 02:18:30 -0500 Date: Fri, 14 Dec 2018 08:18:26 +0100 From: Greg Kroah-Hartman To: Henrik Austad Cc: Linux Kernel Mailing List , stable@vger.kernel.org, Henrik Austad , Peter Zijlstra , juri.lelli@arm.com, bigeasy@linutronix.de, rostedt@goodmis.org, mathieu.desnoyers@efficios.com, jdesfossez@efficios.com, dvhart@infradead.org, bristot@redhat.com, Thomas Gleixner Subject: Re: [PATCH 00/17] Backport rt/deadline crash and the ardous story of FUTEX_UNLOCK_PI to 4.4 Message-ID: <20181214071826.GE31355@kroah.com> References: <1541758065-10952-1-git-send-email-henrik@austad.us> <20181109103531.GA9188@sisyphus.home.austad.us> <20181119112720.GA29334@sisyphus.home.austad.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181119112720.GA29334@sisyphus.home.austad.us> Sender: stable-owner@vger.kernel.org List-ID: On Mon, Nov 19, 2018 at 12:27:21PM +0100, Henrik Austad wrote: > On Fri, Nov 09, 2018 at 11:35:31AM +0100, Henrik Austad wrote: > > On Fri, Nov 09, 2018 at 11:07:28AM +0100, Henrik Austad wrote: > > > From: Henrik Austad > > > > > > Short story: > > > > Sorry for the spam, it looks like I was not very specific in /which/ > > version I targeted this to, as well as not providing a full Cc-list for the > > cover-letter. > > Gentle prod. I realize this was sent out just before plumbers and that > people had pretty packed agendas, so a small nudge to gain a spot closer to > the top of the inbox :) > > This series has now been running on an arm64 system for 9 days without any > issues and pi_stress showed a dramatic improvement from ~30 seconds and up > to several ours (it finally deadlocked at 3.9e9 inversions). > > I'd greatly appreciate if someone could give the list of patches a quick > glance to verify that I got all the required patches and then if it could > be added to 4.4.y. This is a really intrusive series of patches, and without some testing and verification by others, I am really reluctant to take these patches. Why not just move to the 4.9.y tree, or better yet, 4.19.y to resolve this issue for your systems? thanks, greg k-h