From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Galbraith Subject: Re: [PATCH PREEMPT RT] rt-mutex: fix deadlock in device mapper Date: Tue, 21 Nov 2017 18:33:39 +0100 Message-ID: <1511285619.30074.13.camel@gmx.de> References: <20171117145744.t366d2ztxj2qqnco@linutronix.de> <1511030230.12841.42.camel@gmx.de> <1511234430.7672.26.camel@gmx.de> <1511255884.7672.49.camel@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: 8BIT Cc: Thomas Gleixner , Sebastian Siewior , linux-kernel@vger.kernel.org, Ingo Molnar , Steven Rostedt , linux-rt-users@vger.kernel.org To: Mikulas Patocka Return-path: Received: from mout.gmx.net ([212.227.17.21]:64849 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751145AbdKURdz (ORCPT ); Tue, 21 Nov 2017 12:33:55 -0500 In-Reply-To: Sender: linux-rt-users-owner@vger.kernel.org List-ID: On Tue, 2017-11-21 at 11:11 -0500, Mikulas Patocka wrote: > > So, drop the spinlock unplugging and leave only mutex unplugging, > reproduce the deadlock and send the stacktraces. Nah, I reproduced it five years ago.  Is any of that relevant today?  Damned if I know.  Your report was the first I've noticed since. -Mike