From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "J. Bruce Fields" <bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] access: fix outdated NFS information
Date: Fri, 13 Sep 2013 06:28:33 +0200 [thread overview]
Message-ID: <52329471.7050001@gmail.com> (raw)
In-Reply-To: <20130911202210.GB1462-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
On 11.09.2013 22:22, J. Bruce Fields wrote:
> From: "J. Bruce Fields" <bfields-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>
> Note that NFS versions since version 3 support an "access" call so that
> the client doesn't have to guess permissions or id mapping on its own.
>
> (See rfc 1813 sections 1.7 and 3.3.4.)
Thanks, Bruce. Applied.
Cheers,
Michael
> Signed-off-by: J. Bruce Fields <bfields-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> ---
> man2/access.2 | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/man2/access.2 b/man2/access.2
> index 6df68de..3bacab1 100644
> --- a/man2/access.2
> +++ b/man2/access.2
> @@ -209,9 +209,10 @@ Similarly, a DOS file may be found to be "executable," but the
> call will still fail.
> .PP
> .BR access ()
> -may not work correctly on NFS filesystems with UID mapping enabled,
> +may not work correctly on NFSv2 filesystems with UID mapping enabled,
> because UID mapping is done on the server and hidden from the client,
> -which checks permissions.
> +which checks permissions. (NFS versions 3 and higher perform the check on
> +the server.)
> Similar problems can occur to FUSE mounts.
> .SH BUGS
> In kernel 2.4 (and earlier) there is some strangeness in the handling of
>
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: mtk.manpages@gmail.com, linux-nfs@vger.kernel.org,
linux-man@vger.kernel.org
Subject: Re: [PATCH] access: fix outdated NFS information
Date: Fri, 13 Sep 2013 06:28:33 +0200 [thread overview]
Message-ID: <52329471.7050001@gmail.com> (raw)
In-Reply-To: <20130911202210.GB1462@fieldses.org>
On 11.09.2013 22:22, J. Bruce Fields wrote:
> From: "J. Bruce Fields" <bfields@redhat.com>
>
> Note that NFS versions since version 3 support an "access" call so that
> the client doesn't have to guess permissions or id mapping on its own.
>
> (See rfc 1813 sections 1.7 and 3.3.4.)
Thanks, Bruce. Applied.
Cheers,
Michael
> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
> ---
> man2/access.2 | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/man2/access.2 b/man2/access.2
> index 6df68de..3bacab1 100644
> --- a/man2/access.2
> +++ b/man2/access.2
> @@ -209,9 +209,10 @@ Similarly, a DOS file may be found to be "executable," but the
> call will still fail.
> .PP
> .BR access ()
> -may not work correctly on NFS filesystems with UID mapping enabled,
> +may not work correctly on NFSv2 filesystems with UID mapping enabled,
> because UID mapping is done on the server and hidden from the client,
> -which checks permissions.
> +which checks permissions. (NFS versions 3 and higher perform the check on
> +the server.)
> Similar problems can occur to FUSE mounts.
> .SH BUGS
> In kernel 2.4 (and earlier) there is some strangeness in the handling of
>
next prev parent reply other threads:[~2013-09-13 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 20:22 [PATCH] access: fix outdated NFS information J. Bruce Fields
2013-09-11 20:22 ` J. Bruce Fields
[not found] ` <20130911202210.GB1462-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2013-09-13 4:28 ` Michael Kerrisk (man-pages) [this message]
2013-09-13 4:28 ` Michael Kerrisk (man-pages)
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=52329471.7050001@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-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 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.