Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#2581 - Process umask ignored when serving NFSv4.2 share #7388

openwrt-bot opened this issue Nov 8, 2019 · 0 comments

FS#2581 - Process umask ignored when serving NFSv4.2 share #7388

openwrt-bot opened this issue Nov 8, 2019 · 0 comments
flyspray kernel


Copy link

openwrt-bot commented Nov 8, 2019


I am not sure if this is a server-side or client-side problem.

I have an NFS share that I mount from a Fedora 31 workstation. When I mount the share using NFSv4.2, I find that the process umask is ignored when creating files and directories within the share. Files are created with 666 permissions, and directories are created with 777 permissions. Mounting the same share with NFSv4.1 rather than 4.2 works fine.

  1. Mount an NFSv4.2 share from OpenWrt to /mnt on Fedora
  2. mkdir /mnt/foo
  3. ls -ld /mnt/foo

Resulting permissions are 777, but they should be 755, due to a process umask of 0022.

This seems related to a similar Ubuntu report:

I suspect this results from changes due to the RFC "Allowing Inheritable NFSv4 ACLs to Override the Umask:"

See also for a report on the client side.

OpenWrt SNAPSHOT, r11219-34c4741da0 on x86_64
kmod-fs-nfs - 4.19.78-1
kmod-fs-nfs-common - 4.19.78-1
kmod-fs-nfs-common-rpcsec - 4.19.78-1
kmod-fs-nfs-v4 - 4.19.78-1
kmod-fs-nfsd - 4.19.78-1
nfs-kernel-server - 2.4.1-1
nfs-utils-libs - 2.4.1-1

@aparcar aparcar added the kernel label Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
flyspray kernel
None yet

No branches or pull requests

2 participants