From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S934340AbcIVPJX (ORCPT <rfc822;w@1wt.eu>);
        Thu, 22 Sep 2016 11:09:23 -0400
Received: from mail-oi0-f47.google.com ([209.85.218.47]:33427 "EHLO
        mail-oi0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S933580AbcIVPJU (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 22 Sep 2016 11:09:20 -0400
Date: Thu, 22 Sep 2016 10:09:18 -0500
From: Seth Forshee <seth.forshee@canonical.com>
To: Steve French <sfrench@samba.org>, Aurelien Aptel <aaptel@suse.com>
Cc: Sachin Prabhu <sprabhu@redhat.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org,
        stable@vger.kernel.org
Subject: cifs mount regression in 4.8 and 4.4 stable
Message-ID: <20160922150918.GA127053@ubuntu-hedt>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

We've received reports from users of a cifs mount regression in our
4.4-based kernel, e.g. [1]. It is fixed by reverting the follwing commit
from 4.8 which was applied to 4.4 stable:

 a6b5058 fs/cifs: make share unaccessible at root level mountable

Testing against 4.8-rc7 shows that the problem is present there as well.

Thanks,
Seth

[1] http://bugs.launchpad.net/bugs/1626112