Date: Wed, 8 Jul 2015 18:28:23 +0200 (CEST)
From: Fabian Frederick <fabf@skynet.be>
Reply-To: Fabian Frederick <fabf@skynet.be>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
        Alexey Khoroshilov <khoroshilov@ispras.ru>,
        Ian Campbell <ian.campbell@citrix.com>,
        Roger Pau Monne <roger.pau@citrix.com>, Jan Kara <jack@suse.cz>,
        Ian Jackson <Ian.Jackson@eu.citrix.com>,
        Al Viro <viro@zeniv.linux.org.uk>,
        Evgeniy Dushistov <dushistov@mail.ru>, stable@vger.kernel.org
Message-ID: <574518929.1062219.1436372903080.open-xchange@webmail.nmp.proximus.be>
In-Reply-To: <20150708073240.933834626@linuxfoundation.org>
References: <20150708073237.780280770@linuxfoundation.org> <20150708073240.933834626@linuxfoundation.org>
Subject: Re: [PATCH 4.1 54/56] fs/ufs: restore s_lock mutex
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Importance: Medium
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 756
Lines: 30


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...

Regards,
Fabian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/