All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org>
To: linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Pavel Shilovsky
	<piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Mount failure due to restricted access to a point along the mount path
Date: Mon, 04 Feb 2013 21:04:21 +0530	[thread overview]
Message-ID: <510FD4FD.3010001@suse.com> (raw)

Hi all,

I have been looking at the $SUBJECT. And there is already a bug reported
in the samba.org bugzilla

https://bugzilla.samba.org/show_bug.cgi?id=8950

cifs gets "Access denied" while trying to get the root inode. Suppose if
you are trying to mount /share/dir/subdir and if the user doesn't have
access to any of point along the path ie. /share or /dir, mount will fail.

As noted by Jeff Layton in the bug report, this seems to be a known
problem since we started using the shared superblock model. Though we
can work around this problem by providing neccessary permissions for the
entire path, users consider this as a regression. I tend to agree with
them and think that may be we should have addressed this problem before
pushing the shared superblock changes.

>From the changelog it appears that this results in better performance
when we use SMB2.1 leases. How much better performance we are seeing?
Is that worth living with this regression?

Does this affect the CIFS users who are not using SMB2.1 in anyway?


Thanks

-- 
Suresh Jayaraman

             reply	other threads:[~2013-02-04 15:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 15:34 Suresh Jayaraman [this message]
     [not found] ` <510FD4FD.3010001-IBi9RG/b67k@public.gmane.org>
2013-02-04 19:41   ` Mount failure due to restricted access to a point along the mount path Jeff Layton
     [not found]     ` <20130204144152.1c839176-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2013-02-04 19:55       ` Steve French
  -- strict thread matches above, loose matches on Subject: below --
2013-05-10 14:13 Miklos Szeredi
2013-05-10 14:27 ` Jeff Layton
     [not found]   ` <20130510102754.184cd90d-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2013-05-14  8:51     ` Jeff Layton
2013-05-14  8:51       ` Jeff Layton
     [not found]       ` <20130514105119.66a5bc3f-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2013-05-14 10:44         ` Steve French
2013-05-14 10:44           ` Steve French
2013-05-14 11:09           ` Jeff Layton
     [not found]             ` <20130514130906.7f9525bf-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2013-05-14 13:08               ` Steve French
2013-05-14 13:08                 ` Steve French
2013-05-16  6:19         ` Pavel Shilovsky
2013-05-16  6:19           ` Pavel Shilovsky
2013-10-07  3:22     ` Shirish Pargaonkar
2013-10-07  3:22       ` Shirish Pargaonkar

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=510FD4FD.3010001@suse.com \
    --to=sjayaraman-ibi9rg/b67k@public.gmane.org \
    --cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=piastryyy-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.