From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755149AbbCFMTa (ORCPT ); Fri, 6 Mar 2015 07:19:30 -0500 Received: from www.linutronix.de ([62.245.132.108]:54936 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754466AbbCFMT3 (ORCPT ); Fri, 6 Mar 2015 07:19:29 -0500 Date: Fri, 6 Mar 2015 13:19:21 +0100 From: Sebastian Andrzej Siewior To: Steven Rostedt Cc: Thavatchai Makphaibulchoke , Thavatchai Makphaibulchoke , linux-kernel@vger.kernel.org, mingo@redhat.com, tglx@linutronix.de, linux-rt-users@vger.kernel.org Subject: Re: [PATCH 3.14.25-rt22 1/2] rtmutex Real-Time Linux: Fixing kernel BUG at kernel/locking/rtmutex.c:997! Message-ID: <20150306121921.GA10155@linutronix.de> References: <1424395866-81589-1-git-send-email-tmac@hp.com> <1424395866-81589-2-git-send-email-tmac@hp.com> <20150223133719.2b7c604e@gandalf.local.home> <54EBC2DB.3050904@hp.com> <20150223195743.546b2ef0@grimm.local.home> <20150226135630.GD12992@linutronix.de> <20150226090610.7eb0ac61@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20150226090610.7eb0ac61@gandalf.local.home> X-Key-Id: 2A8CF5D1 X-Key-Fingerprint: 6425 4695 FFF0 AA44 66CC 19E6 7B96 E816 2A8C F5D1 User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Steven Rostedt | 2015-02-26 09:06:10 [-0500]: >If we can pull that off and remove all rtmutex trylocks from hardirq >context, I would much rather do that. > >This hocus pocus coding is just going to lead us down the path of the >black arts. I already have a black cat, so I'm good to go. Okay. So what is the fix for v3.14 and other trees where the rtmutex reworked has been integrated? Revert the optimization like I did in v3.18? Sebastian