Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: "Aurélien Aptel" <aurelien.aptel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Miloslav Hůla"
	<miloslav.hula-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 14:08:35 +0200	[thread overview]
Message-ID: <mpsmvb6xb24.fsf@aaptelpc.suse.de> (raw)
In-Reply-To: <0e877de6-0d85-d185-aaa9-f64b058e19b6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

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

-- 
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)

  parent reply	other threads:[~2017-04-24 12:08 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 [this message]
     [not found]     ` <mpsmvb6xb24.fsf-zpEvHKhluMwYitT5tn2FcQ@public.gmane.org>
2017-04-24 15:57       ` Miloslav Hůla

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=mpsmvb6xb24.fsf@aaptelpc.suse.de \
    --to=aurelien.aptel-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=miloslav.hula-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox