Commit 0b4f132
NFS: Ensure the NFS_CAP_SECURITY_LABEL capability is set when appropriate
Commit ce62b11 ("NFS: Split attribute support out from the server
capabilities") removed the logic from _nfs4_server_capabilities() that
sets the NFS_CAP_SECURITY_LABEL capability based on the presence of
FATTR4_WORD2_SECURITY_LABEL in the attr_bitmask of the server's response.
Now NFS_CAP_SECURITY_LABEL is never set, which breaks labelled NFS.
This was replaced with logic that clears the NFS_ATTR_FATTR_V4_SECURITY_LABEL
bit in the newly added fattr_valid field based on the absence of
FATTR4_WORD2_SECURITY_LABEL in the attr_bitmask of the server's response.
This essentially has no effect since there's nothing looks for that bit
in fattr_supported.
So revert that part of the commit, but adding the logic that sets
NFS_CAP_SECURITY_LABEL near where the other capabilities are set in
_nfs4_server_capabilities().
Fixes: ce62b11 ("NFS: Split attribute support out from the server capabilities")
Signed-off-by: Scott Mayhew <smayhew@redhat.com>
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>1 parent f8849e2 commit 0b4f132
1 file changed
Lines changed: 4 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3878 | 3878 | | |
3879 | 3879 | | |
3880 | 3880 | | |
| 3881 | + | |
| 3882 | + | |
| 3883 | + | |
| 3884 | + | |
3881 | 3885 | | |
3882 | 3886 | | |
3883 | 3887 | | |
| |||
3898 | 3902 | | |
3899 | 3903 | | |
3900 | 3904 | | |
3901 | | - | |
3902 | | - | |
3903 | | - | |
3904 | | - | |
3905 | 3905 | | |
3906 | 3906 | | |
3907 | 3907 | | |
| |||
0 commit comments