From: "Miloslav Hůla" <miloslav.hula-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Aurélien Aptel"
<aurelien.aptel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mout.cifs - No such file or directory/Permission denied
Date: Mon, 24 Apr 2017 17:57:52 +0200 [thread overview]
Message-ID: <8f4a5d81-3727-1382-8a00-5b7d8aecb3cc@gmail.com> (raw)
In-Reply-To: <mpsmvb6xb24.fsf-zpEvHKhluMwYitT5tn2FcQ@public.gmane.org>
Dne 24-Apr-17 v 14:08 Aurélien Aptel napsal(a):
> Miloslav Hůla <miloslav.hula-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>> I'm trying to mount NetApp CIFS share, but without success. Connecting
>> it as a network drive or accessing it directly by pasting path into
>> explorer in Windows 8/10 works. smbclient works too.
>
> This looks like good old bso#8950 [1]. You should try a kernel with the
> following commits (4.9 or above, or a kernel where they have been backported):
>
> a6b5058 fs/cifs: make share unaccessible at root level mountable
> 4214ebf Fix memory leaks in cifs_do_mount()
> c1d8b24 Compare prepaths when comparing superblocks
> 348c1bf Move check for prefix path to within cifs_get_root()
> d171356 Fix regression which breaks DFS mounting
>
> 1: https://bugzilla.samba.org/show_bug.cgi?id=8950
In deed it is. With kernel 4.9.0-0.bpo.2-amd64 from jessie-backports
mount works.
Thank you,
Milo
prev parent reply other threads:[~2017-04-24 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 10:59 mout.cifs - No such file or directory/Permission denied Miloslav Hůla
[not found] ` <0e877de6-0d85-d185-aaa9-f64b058e19b6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-04-24 12:08 ` Aurélien Aptel
[not found] ` <mpsmvb6xb24.fsf-zpEvHKhluMwYitT5tn2FcQ@public.gmane.org>
2017-04-24 15:57 ` Miloslav Hůla [this message]
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=8f4a5d81-3727-1382-8a00-5b7d8aecb3cc@gmail.com \
--to=miloslav.hula-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=aurelien.aptel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-cifs-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox