On Fri, 2017-09-22 at 16:15 -0400, Scott Mayhew wrote:
> RFC 1813 section 3.3.8 states
>
> Once the client has performed a successful exclusive
> create, it must issue a SETATTR to set the correct file
> attributes. Until it does so, it should not rely upon any
> of the file attributes, since the server implementation
> may need to overload file metadata to store the verifier.
>
> HP-UX expects the client to send the uid and gid in the post-create
> setattr for exclusive creates. Customers are sometimes seeing bogus
> values because the Linux NFS client is only updating the atime and
> mtime.
I'm sorry, but that is just insanely stupid server behaviour. How do
you guarantee that a second client won't hijack the file by sending
their own SETATTR call before your client has an opportunity to set the
owner?
--
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@xxxxxxxxxxxxxxx
��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
