freebsd-dev/sys/nfsclient
Doug Rabson 5d81e553a2 I believe that the following fix to nfs_vnops.c should do the trick w.r.t.
the problem "when a file is truncated on the server after being written on
a client under NFSv3, the client doesn't see the size drop to zero".
(As you noted, the problem is that NMODIFIED wasn't being cleared by nfs_close
 when it flushed the buffers. After checking through the code, the only place
 where NMODIFIED was used to test for the possibility of dirty blocks was in
 nfs_setattr(). The two cases are safe to do when there aren't dirty blocks,
 so I just took out the tests. Unfortunately, testing for
 v_dirtyblkhd.lh_first being non-null is not sufficient, since there are
 times when the code moves blocks to the clean list and then back to the
 dirty list.)

Submitted by:	rick@snowhite.cis.uoguelph.ca
1995-07-13 17:55:12 +00:00
..
nfs_bio.c Use a consistent blocksize for sizing bufs to avoid panicing the bio system. 1995-07-07 11:01:31 +00:00
nfs_nfsiod.c
nfs_node.c
nfs_socket.c
nfs_subs.c NOTE: libkvm, w, ps, 'top', and any other utility which depends on struct 1995-07-13 08:48:48 +00:00
nfs_vfsops.c Use a consistent blocksize for sizing bufs to avoid panicing the bio system. 1995-07-07 11:01:31 +00:00
nfs_vnops.c I believe that the following fix to nfs_vnops.c should do the trick w.r.t. 1995-07-13 17:55:12 +00:00
nfs.h
nfsargs.h
nfsdiskless.h
nfsm_subs.h
nfsmount.h
nfsnode.h
nfsstats.h