Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3469984imu; Mon, 28 Jan 2019 05:31:34 -0800 (PST) X-Google-Smtp-Source: ALg8bN4PDcvHoZ8vVvulSMaONfoiViXYEu+UtP4L0hTjx64UTzqsYLhLMNPetKwg9fYfBCu/qMgk X-Received: by 2002:a63:554b:: with SMTP id f11mr20416735pgm.37.1548682294329; Mon, 28 Jan 2019 05:31:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548682294; cv=none; d=google.com; s=arc-20160816; b=WVEG35Gt4nTJFkWEZrhPynMJ0mCq6/9M0gvi1Yt7jalVv3p+Jw+kX2uFbie1FAwU10 mroALYoRT+A4g1q0crxQwT5P7YtsrEy5X9bx1ZfYqfdmrcu6hBmjsdt61K6sUyn599iT 8UQ5ZHNI5cz2Lp/mEz8m/ZozlqqOYSrQpVqNgJ4Otzmt1IXDpHhRiwZEGmX4tCC8htJx rt8BvGbgwfXHyASelsflnF1T5/DFh38eYEr33Q9TWly83SQJsA12U4hYkyfB5jTJ7bdA WF7LYlSInyV23pjzWgbzrUCavKfeCqqyO802co+eS36O4txWlZX5uLgYnx+K+aYG9cx8 7oNQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=3LUGEaQ88zHm38UD7tIMrwxzcpj3VrE9kzOBHmFEw6A=; b=RkiLwdBka4a4YFxatarVb+ccF3soIbCYOyooP0Mm6kQ6+qC8KcditAXhs+LNtE11K/ FxbtDIVgjYc0GdAsQfmHCZk9xvwmJrLmcZTSfTp3RCLvJF0QDj+tPBfBycVx6nMP+rbo SYuxyamDmTXqpwlLI6cYJ6VeRUUFAW6s9BtRmdx7WQxUItBySyM/Fy21Pd0j7OJ5CR07 lccBGVdKcJQfeMXPfHp0ZQQMPgRkG20rU6mLWpXI5dueIlv67t8kbnEDOrx2sFATum5b VU5StmwD18DnfWb64A36cMMjU+CA5BtmkEA6Eqfh+t+Du/wVgVzMEZo95pEqUBng3JWm PPDw== ARC-Authentication-Results: i=1; mx.google.com; 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 c3si5021762plr.178.2019.01.28.05.31.18; Mon, 28 Jan 2019 05:31:34 -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; 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 S1726749AbfA1NbH (ORCPT + 99 others); Mon, 28 Jan 2019 08:31:07 -0500 Received: from mx2.suse.de ([195.135.220.15]:43114 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726647AbfA1NbH (ORCPT ); Mon, 28 Jan 2019 08:31:07 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id D90A3AF6F; Mon, 28 Jan 2019 13:31:05 +0000 (UTC) Received: by quack2.suse.cz (Postfix, from userid 1000) id 2B3771E3FEF; Mon, 28 Jan 2019 14:31:03 +0100 (CET) Date: Mon, 28 Jan 2019 14:31:03 +0100 From: Jan Kara To: Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, Jan Kara , Jens Axboe Subject: Re: [PATCH 4.4 068/104] loop: Fold __loop_release into loop_release Message-ID: <20190128133103.GD27972@quack2.suse.cz> References: <20190124190154.968308875@linuxfoundation.org> <20190124190203.062416837@linuxfoundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190124190203.062416837@linuxfoundation.org> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 24-01-19 20:19:57, Greg Kroah-Hartman wrote: > 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 > Hello Greg! This and the following two (patches 69 & 70) loop patches are just preparatory cleanups for commits 0da03cab87e632 "loop: Fix deadlock when calling blkdev_reread_part()" and 1dded9acf6dc9a "loop: Avoid circular locking dependency between loop_ctl_mutex and bd_mutex". As such they don't fix anything and it doesn't make sense to carry them in stable unless someone backports also the other patches in the series including the fixes themselves (which honestly I don't think is worth it for stable). Honza > --- > 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); > } > > > -- Jan Kara SUSE Labs, CR