From: Sachin Prabhu <sprabhu@redhat.com>
To: Seth Forshee <seth.forshee@canonical.com>,
Steve French <sfrench@samba.org>,
Aurelien Aptel <aaptel@suse.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: cifs mount regression in 4.8 and 4.4 stable
Date: Thu, 22 Sep 2016 16:17:09 +0100 [thread overview]
Message-ID: <1474557429.14139.10.camel@redhat.com> (raw)
In-Reply-To: <20160922150918.GA127053@ubuntu-hedt>
On Thu, 2016-09-22 at 10:09 -0500, Seth Forshee wrote:
> 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
Hello Seth,
We have identified some regressions introduced by the mentioned patch
These include
a) mounting of DFS shares breaks. The fix is included in Steve's tree
at
https://git.samba.org/?p=sfrench/cifs-2.6.git;a=commit;h=de5233745cd59c
f5853d963ad216067788a87594
b) mounting of the same share with different paths breaks. Fixed by
upstream commit c1d8b24d18192764fe82067ec6aa8d4c3bf094e0
c) memory leaks in mounting fixed by upstream 4214ebf4654798309
364d0c678b799e402f38288
Can you please share any other reports not mentioned above?
Sachin Prabhu
next prev parent reply other threads:[~2016-09-22 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 15:09 cifs mount regression in 4.8 and 4.4 stable Seth Forshee
2016-09-22 15:15 ` Greg Kroah-Hartman
2016-09-22 15:17 ` Sachin Prabhu [this message]
[not found] ` <1474557429.14139.10.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-09-22 15:27 ` Seth Forshee
2016-09-23 12:01 ` Seth Forshee
2016-11-17 9:47 ` Greg Kroah-Hartman
[not found] ` <20161117094725.GB2116-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2016-11-17 10:11 ` Sachin Prabhu
2016-11-17 10:31 ` Greg Kroah-Hartman
2016-11-17 10:17 ` Aurélien Aptel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1474557429.14139.10.camel@redhat.com \
--to=sprabhu@redhat.com \
--cc=aaptel@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seth.forshee@canonical.com \
--cc=sfrench@samba.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).