[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150710173859.GH10580@kroah.com>
Date: Fri, 10 Jul 2015 10:38:59 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Luis Henriques <luis.henriques@...onical.com>
Cc: Fabian Frederick <fabf@...net.be>, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Alexey Khoroshilov <khoroshilov@...ras.ru>,
Ian Campbell <ian.campbell@...rix.com>,
Roger Pau Monne <roger.pau@...rix.com>,
Jan Kara <jack@...e.cz>,
Ian Jackson <Ian.Jackson@...citrix.com>,
Al Viro <viro@...iv.linux.org.uk>,
Evgeniy Dushistov <dushistov@...l.ru>, stable@...r.kernel.org
Subject: Re: [PATCH 4.1 54/56] fs/ufs: restore s_lock mutex
On Thu, Jul 09, 2015 at 03:37:19PM +0100, Luis Henriques wrote:
> On Wed, Jul 08, 2015 at 02:32:30PM -0700, Greg Kroah-Hartman wrote:
> > On Wed, Jul 08, 2015 at 10:32:08AM -0700, Greg Kroah-Hartman wrote:
> > > On Wed, Jul 08, 2015 at 06:28:23PM +0200, Fabian Frederick wrote:
> > > >
> > > > Hello Greg,
> > > >
> > > > Here's the complete list of linux-next/UFS patches needed
> > > > to stop regressions in write mode:
> > > >
> > > > 13b987ea2758
> > > > fs/ufs: revert "ufs: fix deadlocks introduced by sb mutex merge"
> > > >
> > > > cdd9eefdf905
> > > > fs/ufs: restore s_lock mutex
> > > >
> > > > 12ecbb4b1d76
> > > > ufs: Fix warning from unlock_new_inode()
> > > >
> > > > 514d748f69c9
> > > > ufs: Fix possible deadlock when looking up directories
>
> I don't think the 2 commits above are appropriate for the 3.14 and
> 3.10 kernels as they fix commit e4502c63f56a ("ufs: deal with
> nfsd/iget races"), which isn't in these kernels
Ah, you are right, thanks, don't know how I missed that. Now removed.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists