Home
last modified time | relevance | path

Searched hist:"1750 d929b08764dd293d5bdddaa9bc4d3f94d228" (Results 1 – 3 of 3) sorted by relevance

/openbmc/linux/fs/nfs/
H A Dnfs3proc.cdiff 1750d929b08764dd293d5bdddaa9bc4d3f94d228 Wed Jul 26 11:00:21 CDT 2017 Anna Schumaker <Anna.Schumaker@Netapp.com> NFS: Don't compare apples to elephants to determine access bits

The NFS_ACCESS_* flags aren't a 1:1 mapping to the MAY_* flags, so
checking for MAY_WHATEVER might have surprising results in
nfs*_proc_access(). Let's simplify this check when determining which
bits to ask for, and do it in a generic place instead of copying code
for each NFS version.

Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
H A Ddir.cdiff 1750d929b08764dd293d5bdddaa9bc4d3f94d228 Wed Jul 26 11:00:21 CDT 2017 Anna Schumaker <Anna.Schumaker@Netapp.com> NFS: Don't compare apples to elephants to determine access bits

The NFS_ACCESS_* flags aren't a 1:1 mapping to the MAY_* flags, so
checking for MAY_WHATEVER might have surprising results in
nfs*_proc_access(). Let's simplify this check when determining which
bits to ask for, and do it in a generic place instead of copying code
for each NFS version.

Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
H A Dnfs4proc.cdiff 1750d929b08764dd293d5bdddaa9bc4d3f94d228 Wed Jul 26 11:00:21 CDT 2017 Anna Schumaker <Anna.Schumaker@Netapp.com> NFS: Don't compare apples to elephants to determine access bits

The NFS_ACCESS_* flags aren't a 1:1 mapping to the MAY_* flags, so
checking for MAY_WHATEVER might have surprising results in
nfs*_proc_access(). Let's simplify this check when determining which
bits to ask for, and do it in a generic place instead of copying code
for each NFS version.

Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>