[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150708213230.GB31433@kroah.com>
Date: Wed, 8 Jul 2015 14:32:30 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Fabian Frederick <fabf@...net.be>
Cc: 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 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
> >
> > e4f95517f182
> > fs/ufs: restore s_lock mutex_init()
> >
> > but I only see the 2 first ones in your 4.0/4.1 stable reviews...
>
> That's because those other ones weren't marked with a stable tag so I
> didn't catch them :(
>
> I'll queue them up now, thanks for letting me know.
The last one didn't apply to 3.10 or 3.14, but all the others seemed
good, now applied.
thanks,
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