Re: [PATCH 4.1 54/56] fs/ufs: restore s_lock mutex

[Luis Henriques]

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

Cheers,
--
Luís

> > > 
> > > 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 stable" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/