Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2405920imu; Thu, 24 Jan 2019 12:12:18 -0800 (PST) X-Google-Smtp-Source: ALg8bN6jJkgT2BYxq8N63FfFzZs7r+pRA9Qv1noGeffpFPTh/62ziDoxyJt2+FkOz4DLTKEnwn4R X-Received: by 2002:a63:e711:: with SMTP id b17mr7030181pgi.363.1548360738447; Thu, 24 Jan 2019 12:12:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548360738; cv=none; d=google.com; s=arc-20160816; b=nRydYDWH2ePZ2ZZuL+nuVx4i103rAdp24Eyxd4vGwpD2otYnmIioh6feONovggEKKd u6fObCXJqmF/ZF88T0SRNKBYlG2+ppMx/99sAObz2cJRWQUAipCd9YEQETiL1dcr1dFu NCsGLAhDIDe8wC+m5Wj0QxIKkKkMWfv+0melwl5+9QLkwWA3BrbZknorpxvcN3raq1+2 Q24mymF8IBVFagBJLSy9tKnhy8YHXDrVmw2cvjEXT+Z2QjawM8UTzd9EwAAv7/ZbuKC1 Dazym5Iy0nBRj6lBiBj8T6m8NOqZ/2gdR0WVAc5tOLNRGHjOscCgx/qWv4fWRlgQ/bVx esUA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=2KHIatbvzpfCHvsS+PYdMWAjIPWVAWqCpCDbrDfXJ1o=; b=tPloGaIzANCDPk8S6uBX2bs0NaUDaXjRFr0v7PxtghEKGTz/EokKzAiPcJzJS8NvXQ +X17zqIJujWK3K+FFBQPSOOVIGV3SpMp628d04Uu5LdvD19csM2R3GZ0vzRgyBqypJkE 5mqRhdaBXih0GCKkAjdVSpziWHpNUO+tkKuVpM+GjbXxu+nKEj75ID8abRS/y6bQt46m eGgklZ9moRghlqXEDkTy44EV9KZ+4ReuSSztuaeje40FFtfaRER5kSn5eB0eXFDIBN5E qUy9iHxgWb/1WTKJvmIT9Mp5mCZ/jMqZoP6cpPo8nYJyRsar94WZ6xb3v3A+ONH00oe1 uHaQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=FmZcs3sF; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 31si10841121plz.263.2019.01.24.12.12.03; Thu, 24 Jan 2019 12:12:18 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=FmZcs3sF; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730681AbfAXT1C (ORCPT + 99 others); Thu, 24 Jan 2019 14:27:02 -0500 Received: from mail.kernel.org ([198.145.29.99]:53146 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729218AbfAXT1A (ORCPT ); Thu, 24 Jan 2019 14:27:00 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 2C7C2218FC; Thu, 24 Jan 2019 19:26:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1548358019; bh=kCVIncFlZ5IpvsY0PR9TEQ+x0u0dPrOizGlIg4v8FEo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=FmZcs3sFwIP+SwLO/XIC85a34ipcEKVcoWIBfM2Vm281RKxH49WXGU/aH0HgroAG8 gjqqlKnso2aRnCvqpz1iZ7VkSLAqSoQ2thmxgNlSeC6DDCEjD99f15NYuLC2Y9+bH1 QycC8Tkd6Ubk/qzqRm/rft9sTFO7qBX6muhTinHI= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Jan Kara , Jens Axboe Subject: [PATCH 4.4 068/104] loop: Fold __loop_release into loop_release Date: Thu, 24 Jan 2019 20:19:57 +0100 Message-Id: <20190124190203.062416837@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190124190154.968308875@linuxfoundation.org> References: <20190124190154.968308875@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.4-stable review patch. If anyone has any objections, please let me know. ------------------ From: Jan Kara commit 967d1dc144b50ad005e5eecdfadfbcfb399ffff6 upstream. __loop_release() has a single call site. Fold it there. This is currently not a huge win but it will make following replacement of loop_index_mutex more obvious. Signed-off-by: Jan Kara Signed-off-by: Jens Axboe Signed-off-by: Greg Kroah-Hartman --- drivers/block/loop.c | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) --- a/drivers/block/loop.c +++ b/drivers/block/loop.c @@ -1586,12 +1586,15 @@ out: return err; } -static void __lo_release(struct loop_device *lo) +static void lo_release(struct gendisk *disk, fmode_t mode) { + struct loop_device *lo; int err; + mutex_lock(&loop_index_mutex); + lo = disk->private_data; if (atomic_dec_return(&lo->lo_refcnt)) - return; + goto unlock_index; mutex_lock(&loop_ctl_mutex); if (lo->lo_flags & LO_FLAGS_AUTOCLEAR) { @@ -1601,7 +1604,7 @@ static void __lo_release(struct loop_dev */ err = loop_clr_fd(lo); if (!err) - return; + goto unlock_index; } else { /* * Otherwise keep thread (if running) and config, @@ -1611,12 +1614,7 @@ static void __lo_release(struct loop_dev } mutex_unlock(&loop_ctl_mutex); -} - -static void lo_release(struct gendisk *disk, fmode_t mode) -{ - mutex_lock(&loop_index_mutex); - __lo_release(disk->private_data); +unlock_index: mutex_unlock(&loop_index_mutex); }