From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f67.google.com ([209.85.160.67]:45555 "EHLO mail-pl0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752479AbeCZXQe (ORCPT ); Mon, 26 Mar 2018 19:16:34 -0400 Received: by mail-pl0-f67.google.com with SMTP id n15-v6so12907723plp.12 for ; Mon, 26 Mar 2018 16:16:34 -0700 (PDT) From: Omar Sandoval To: linux-block@vger.kernel.org Cc: Jens Axboe , kernel-team@fb.com, linux-fsdevel@vger.kernel.org Subject: [PATCH 0/2] loop: don't hang on lo_ctl_mutex in ioctls Date: Mon, 26 Mar 2018 16:16:24 -0700 Message-Id: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: From: Omar Sandoval Hi, Jens, We hit an issue where a loop device on NFS (yes, I know) got stuck and a bunch of losetup processes got stuck in uninterruptible sleep waiting for lo_ctl_mutex as a result. Calling into the filesystem while holding lo_ctl_mutex isn't necessary, and there's no reason to be uninterruptible here. These two patches fix this issue, based on your for-next branch. Thanks! Omar Sandoval (2): loop: don't call into filesystem while holding lo_ctl_mutex loop: use interruptible lock in ioctls drivers/block/loop.c | 65 +++++++++++++++++++++++++++++++++------------------- 1 file changed, 42 insertions(+), 23 deletions(-) -- 2.16.2