nfsd: update create verifier comment
[ Upstream commit 2336d696862186fd4a6ddd1ea0cb243b3e32847c ] I don't know if that Solaris behavior matters any more or if it's still possible to look up that bug ID any more. The XFS behavior's definitely still relevant, though; any but the most recent XFS filesystems will lose the top bits. Reported-by: Frank S. Filz <ffilzlnx@mindspring.com> Signed-off-by: J. Bruce Fields <bfields@redhat.com> Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
parent
a90593a639
commit
39e2c3b956
1 changed files with 2 additions and 1 deletions
|
@ -1430,7 +1430,8 @@ do_nfsd_create(struct svc_rqst *rqstp, struct svc_fh *fhp,
|
|||
|
||||
if (nfsd_create_is_exclusive(createmode)) {
|
||||
/* solaris7 gets confused (bugid 4218508) if these have
|
||||
* the high bit set, so just clear the high bits. If this is
|
||||
* the high bit set, as do xfs filesystems without the
|
||||
* "bigtime" feature. So just clear the high bits. If this is
|
||||
* ever changed to use different attrs for storing the
|
||||
* verifier, then do_open_lookup() will also need to be fixed
|
||||
* accordingly.
|
||||
|
|
Loading…
Reference in a new issue