diff options
| author | Trond Myklebust <trond.myklebust@fys.uio.no> | 2004-08-23 10:18:16 -0400 |
|---|---|---|
| committer | Trond Myklebust <trond.myklebust@fys.uio.no> | 2004-08-23 10:18:16 -0400 |
| commit | e143b1c817e8403679a39253194cd5b176cfcd53 (patch) | |
| tree | 278e022186b37362e75c8eec2dc055ca6e952020 /kernel/timer.c | |
| parent | 9053c5750b8886eb86b847281c51dfa899cf9f2e (diff) | |
NFSv2: In the NFSv3 RFC, the sattr3 structure passed in the SETATTR
call allows for the client to request that the mtime and/or atime
of an inode be set to the current server time, the given (client)
time, or not changed. The set-to-current-server value is used
when you run "touch file" on the client.
The NFSv2 RFC defines no such encoding for the sattr structure.
However Solaris and Irix machine obey a convention where passing
the invalid value mtime.useconds=1000000 means "set both mtime and
atime to the current server time". The convention is documented
in the book "NFS Illustrated" by Brent Callaghan. The patch below
implements this convention for the Linux client and server (hence
multiple To:s).
Signed-off-by: Greg Banks <gnb@sgi.com>
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
Diffstat (limited to 'kernel/timer.c')
0 files changed, 0 insertions, 0 deletions