From: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
To: sean finney <seanius-ADwgVSpYHhHR7s880joybQ@public.gmane.org>
Cc: Terrence Shipclark
<terrence.shipclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Pavel Shilovsky <piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.org>
Subject: Re: cifs and win2k8
Date: Sun, 23 Oct 2011 06:55:34 -0400 [thread overview]
Message-ID: <20111023065534.566a0aad@corrin.poochiereds.net> (raw)
In-Reply-To: <20111023103003.GA6132-Znhnm/lQSyjxW5zecs3cv0EOCMrvLtNR@public.gmane.org>
On Sun, 23 Oct 2011 12:30:03 +0200
sean finney <seanius-ADwgVSpYHhHR7s880joybQ@public.gmane.org> wrote:
> Hello Terrence,
>
> On Fri, Oct 21, 2011 at 07:18:20AM -0400, Terrence Shipclark wrote:
> > I have been attempting to get the cifs kernel modules to mount the
> > win2k8 dfs at my workplace. I did finally manage to get
> > the dfs to mount after modifying the kernel module with this small patch
>
> I believe this should already be fixed (in a more correct fashion) in >= 3.0.
>
> > Within the dfs tree there is a referral to //server/share$/folder.
> > My user has access to //server/share$/folder, however do not have
> > access to
> > //server/$share. While following the referral the cifs module does a
> > QUERY_PATH_INFO on \\server\share$\folder, and then is followed up
> > by a QUERY_PATH_INFO on \\server\share$\ which rightfully returns a
> > STATUS_ACCESS_DENIED from the server.
>
> I've also noticed that the mounting process seems to query more than
> it should, but I've taken the easy way out and asked the local windows
> admin to add "traverse filesystem" and "read attributes" permissions on
> the parent folders, which should be enough. I suspect that there is a
> "real fix" to avoid this, but haven't looked too hard myself.
>
>
I believe this is a known bug...
3.0 got a patchset to allow superblocks to be shared, but that
regressed the above use case (mounting a directory that you have access
to but not the stuff below it).
Pavel had some patches that he was going to propose to fix it, but
discussion of them sort of fell off. Pavel, did you ever come up with
something that worked here?
--
Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
next prev parent reply other threads:[~2011-10-23 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 11:18 cifs and win2k8 Terrence Shipclark
[not found] ` <4EA154FC.3090601-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-10-21 11:20 ` Terrence Shipclark
2011-10-23 10:30 ` sean finney
[not found] ` <20111023103003.GA6132-Znhnm/lQSyjxW5zecs3cv0EOCMrvLtNR@public.gmane.org>
2011-10-23 10:55 ` Jeff Layton [this message]
[not found] ` <20111023065534.566a0aad-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-10-23 19:10 ` Pavel Shilovsky
2011-10-24 7:35 ` sean finney
[not found] ` <20111024073534.GB7086-Znhnm/lQSyjxW5zecs3cv0EOCMrvLtNR@public.gmane.org>
2011-11-01 18:13 ` Pavel Shilovsky
[not found] ` <1320171185-11150-1-git-send-email-piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.org>
2011-11-01 19:56 ` Pavel Shilovsky
[not found] ` <CAKywueRjR+UNg98odoe8x2WmnqdiCtEa_UgwnKt-8AEi0XRFdQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-10 13:24 ` Jeff Layton
2011-11-10 13:38 ` Pavel Shilovsky
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=20111023065534.566a0aad@corrin.poochiereds.net \
--to=jlayton-eunubhrolfbytjvyw6ydsg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.org \
--cc=seanius-ADwgVSpYHhHR7s880joybQ@public.gmane.org \
--cc=terrence.shipclark-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