This looks right, but I note that NFSVNO_EXSTRICTACCESS is zero, so this condition is always false anyway...?

Yes, as markj@ notes, the change is harmless
and mostly meaningless. The NFSVNO_EXSTRICTACCESS()
is a placeholder for some site that might not want to let
the file "owner" get access despite mode bits.

The "owner override" is a hack that has existed forever
in NFS, since applications often create files with O_WRONLY,
but mode 444. This works for POSIX, but would make NFS
writes fail, since they check mode on every write, instead of
just at POSIX open(). The hack is to always allow the file owner
to have write access.

Without the hack, lots of applications would break over NFS,
so I doubt anyone would enable NFSVNO_EXSTRICTACCESS().
{ No one has ever even wanted an export flag for it. }