From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752663AbdKUDUr convert rfc822-to-8bit (ORCPT <rfc822;w@1wt.eu>);
        Mon, 20 Nov 2017 22:20:47 -0500
Received: from mout.gmx.net ([212.227.17.20]:62692 "EHLO mout.gmx.net"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752332AbdKUDUp (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 20 Nov 2017 22:20:45 -0500
Message-ID: <1511234430.7672.26.camel@gmx.de>
Subject: Re: [PATCH PREEMPT RT] rt-mutex: fix deadlock in device mapper
From: Mike Galbraith <efault@gmx.de>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Sebastian Siewior <bigeasy@linutronix.de>,
        linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>, Steven Rostedt <rostedt@goodmis.org>,
        linux-rt-users@vger.kernel.org
Date: Tue, 21 Nov 2017 04:20:30 +0100
In-Reply-To: <alpine.LRH.2.02.1711201607230.24006@file01.intranet.prod.int.rdu2.redhat.com>
References: <alpine.LRH.2.02.1711131245580.23280@file01.intranet.prod.int.rdu2.redhat.com>
         <20171117145744.t366d2ztxj2qqnco@linutronix.de>
         <1511030230.12841.42.camel@gmx.de>
         <alpine.LRH.2.02.1711201607230.24006@file01.intranet.prod.int.rdu2.redhat.com>
Content-Type: text/plain; charset="ISO-8859-15"
X-Mailer: Evolution 3.20.5 
Mime-Version: 1.0
Content-Transfer-Encoding: 8BIT
X-Provags-ID: V03:K0:W5ABLC33jJcYa+77+4r2NLQNpE5th+mnscHU/a5C3Tss65GAN/p
 EwxWBkYG/mG5b8WfbRDTwn2xcFnxwbBwlnYLhLWf1scNuhcY86i4NWp+hxS2DhSybVJenwM
 af4P36ueF2k3MyTe6l4kDb2OzbEOroREO36wbySm+G8fEQmi/RI1WTh4vV5rST+tVHRkOA0
 GKJMZ+wGIegkAT4sz2uCg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:RxGcYB2s8hw=:QqBLPqYVm5cQdg1GXnfJCi
 1Ue4LUoJxhRSclcD7whIuHtToRgq9P8yoafjgEl0gouXAL5DZWDoVCetn0IfNpY2R7Irc/Gfo
 KDo/Qo+Gq0eVFla9e2TPiY3tfzMuD3DV6GEBKCrGSvk6MwxTFfN5Sf7rmrjUGIMAOj3NJjzU/
 EdyKFBP6AR6sg+q54wau1cdsmDqW/Yn/D6MgJUieqTBmygBXy/bBDuabMWj8YJxCnzhEsjAIv
 XVYYb2vBAH5nUbOE/rwBRT78byjoPJYImYZU2ZVKClmJ/UdGHnOOviNkdvovhqmRRbaEts43N
 KAPfsv/oVJXiixbcA/8gbTXu4P89jMRK9CBu648mgvNUkFqmn2RNLLVws98OLr8f3PHjx687r
 2qg3pDYwg2aKkO8gpbZkMrgkgG8SHKMbuvo2BLzVslNgdlhU8L8KP4JqrD3xLGxUTlG4ruzTJ
 nyLp8HRzDNSNL/cKCMcZ51THRKvWN54ab2EkaP7ch1ikRuhdIiACrJJ1JY6/vYgtGmIeZxTf6
 uo941OKU7eS2a8qXSTSLNy5L9uVPtmpOkA3gYL1ZOE6/MkJENp+ytSZ2F6Jl8WtMJ6O9h+0Hn
 a20Odhyv4Z/4IDUzlaB3IkBfzA6lAY3HePcy8i0CYD8zniwt+33cZevnQJbctCCXknC23GcO7
 Bm75phXy6pq3CTjAmcl5OLOkIwBNDg6hz3SLrhDum0OFd5krcLZroiYRrfhC9N4w4khN/R4vR
 ZXThZg5JEQJO9mz0mHR20tRxLBPWRkpGjpts/QenScZr1urBfJF3mgxRaJ1Zt/CXHzO/Ju32d
 DwF1HhZrv0PLJXutyunlPSKId12r9h121cHVK1g6sW6eG6wPEk=
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, 2017-11-20 at 16:33 -0500, Mikulas Patocka wrote:
> 
> Is there some specific scenario where you need to call 
> blk_schedule_flush_plug from rt_spin_lock_fastlock?

Excellent question.  What's the difference between not getting IO
started because you meet a mutex with an rt_mutex under the hood, and
not getting IO started because you meet a spinlock with an rt_mutex
under the hood?  If just doing the mutex side puts this thing back to
sleep, I'm happy.

	-Mike