[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190130073053.GA4665@kroah.com>
Date: Wed, 30 Jan 2019 08:30:53 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Jan Kara <jack@...e.cz>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Jens Axboe <axboe@...nel.dk>
Subject: Re: [PATCH 4.4 068/104] loop: Fold __loop_release into loop_release
On Mon, Jan 28, 2019 at 02:31:03PM +0100, Jan Kara wrote:
> 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 <jack@...e.cz>
> >
> > 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 <jack@...e.cz>
> > Signed-off-by: Jens Axboe <axboe@...nel.dk>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> >
>
> 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).
Ah, you are right, sorry about that. I was backporting the loop fixes
and these ended up working on 4.4.y, but as you say, were not needed
unless the later patches also showed up. I'll go revert them now,
thanks.
greg k-h
Powered by blists - more mailing lists