All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: Sachin Prabhu <sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Steve French <sfrench-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>,
	Aurelien Aptel <aaptel-IBi9RG/b67k@public.gmane.org>,
	Greg Kroah-Hartman
	<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: cifs mount regression in 4.8 and 4.4 stable
Date: Fri, 23 Sep 2016 07:01:45 -0500	[thread overview]
Message-ID: <20160923120145.GA51563@ubuntu-hedt> (raw)
In-Reply-To: <20160922152756.GB127053@ubuntu-hedt>

On Thu, Sep 22, 2016 at 10:27:56AM -0500, Seth Forshee wrote:
> On Thu, Sep 22, 2016 at 04:17:09PM +0100, Sachin Prabhu wrote:
> > 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
> 
> I saw those, but none of the ones already in Linus's tree fix the
> problem.
> 
> > 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
> 
> However this one isn't in Linus's tree yet.
> 
> I'm not certain what circumstances cause the failure, but based on what
> I see in dmesg it looks likely that this one is the fix. I'll get some
> testing with this applied.

Looks like this is is the fix we need. Thanks for your help.

Seth

WARNING: multiple messages have this Message-ID (diff)
From: Seth Forshee <seth.forshee@canonical.com>
To: Sachin Prabhu <sprabhu@redhat.com>
Cc: Steve French <sfrench@samba.org>,
	Aurelien Aptel <aaptel@suse.com>,
	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: Fri, 23 Sep 2016 07:01:45 -0500	[thread overview]
Message-ID: <20160923120145.GA51563@ubuntu-hedt> (raw)
In-Reply-To: <20160922152756.GB127053@ubuntu-hedt>

On Thu, Sep 22, 2016 at 10:27:56AM -0500, Seth Forshee wrote:
> On Thu, Sep 22, 2016 at 04:17:09PM +0100, Sachin Prabhu wrote:
> > 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
> 
> I saw those, but none of the ones already in Linus's tree fix the
> problem.
> 
> > 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
> 
> However this one isn't in Linus's tree yet.
> 
> I'm not certain what circumstances cause the failure, but based on what
> I see in dmesg it looks likely that this one is the fix. I'll get some
> testing with this applied.

Looks like this is is the fix we need. Thanks for your help.

Seth

  reply	other threads:[~2016-09-23 12:01 UTC|newest]

Thread overview: 17+ 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:15   ` Greg Kroah-Hartman
2016-09-22 15:17 ` Sachin Prabhu
     [not found]   ` <1474557429.14139.10.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-09-22 15:27     ` Seth Forshee
2016-09-22 15:27       ` Seth Forshee
2016-09-23 12:01       ` Seth Forshee [this message]
2016-09-23 12:01         ` Seth Forshee
2016-11-17  9:47         ` Greg Kroah-Hartman
2016-11-17  9:47           ` Greg Kroah-Hartman
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:11               ` Sachin Prabhu
2016-11-17 10:31               ` Greg Kroah-Hartman
2016-11-17 10:31                 ` Greg Kroah-Hartman
2016-11-17 10:17             ` Aurélien Aptel
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=20160923120145.GA51563@ubuntu-hedt \
    --to=seth.forshee-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
    --cc=aaptel-IBi9RG/b67k@public.gmane.org \
    --cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sfrench-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org \
    --cc=sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.