From: "Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>
To: Robin Blanchard
<robin.blanchard-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-cifs\@vger.kernel.org"
<linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: cifs.ko + smb 3.0 + DFS fails (though direct mount succeeds)
Date: Fri, 16 Jun 2017 11:06:30 +0200 [thread overview]
Message-ID: <mpsmv98ti7d.fsf@aaptelpc.suse.de> (raw)
In-Reply-To: <CAJUwKM25Kd-BHgPNXHkTtvYvK1Ad5uaLkooG6i4H+kawDL1ACg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Robin,
Robin Blanchard <robin.blanchard-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Thanks, Steve.
>
> Given WannaCry (and its derivatives), many shops are disabling SMBv1
> entirely (not necessarily a bad idea). Any idea as to when the
> aforementioned fixes might be pushed downstream? I've tested Ubuntu
> 17.04 with the same results (DFS fails with SMB > v1).
>
> Status code returned 0xc0000016 STATUS_MORE_PROCESSING_REQUIRED
> Status code returned 0xc0000257 STATUS_PATH_NOT_COVERED
> CIFS VFS: cifs_mount failed w/return code = -38
>
> # uname -r
> 4.10.0-22-generic
Unless canonical has backported my changes you need at least linux 4.11.
Cheers,
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2017-06-16 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 20:09 cifs.ko + smb 3.0 + DFS fails (though direct mount succeeds) Robin Blanchard
[not found] ` <CAJUwKM3-U2yRHB5O-R19wmzj1-yrO3sU_b8+xVCFaFwsZRWtTA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-20 20:14 ` Steve French
[not found] ` <CAH2r5mvn_Z5B=kYza1gAr3SkPX+kwKmXBEXcTBL327zcW8FP-g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-14 18:18 ` Robin Blanchard
[not found] ` <CAJUwKM25Kd-BHgPNXHkTtvYvK1Ad5uaLkooG6i4H+kawDL1ACg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-16 9:06 ` Aurélien Aptel [this message]
[not found] ` <mpsmv98ti7d.fsf-zpEvHKhluMwYitT5tn2FcQ@public.gmane.org>
2017-06-16 15:42 ` Christian Garling
[not found] ` <CDE2E2CE-EE67-44AE-A0C8-D3AFF6EAAA01-JDaHaePr6SMW6PBduJaimg@public.gmane.org>
2017-06-19 10:59 ` Aurélien Aptel
[not found] ` <58abb375-f7fb-58ec-4786-9ebd202fffa3@cg-networks.de>
[not found] ` <58abb375-f7fb-58ec-4786-9ebd202fffa3-JDaHaePr6SMW6PBduJaimg@public.gmane.org>
2017-06-20 12:02 ` Aurélien Aptel
2017-06-20 14:14 ` Robin Blanchard
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=mpsmv98ti7d.fsf@aaptelpc.suse.de \
--to=aaptel-ibi9rg/b67k@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robin.blanchard-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@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.