yamt@mwd.biglobe.ne.jp (YAMAMOTO Takashi) writes:

>> thorpej@shagadelic.org said:
>> > This sounds like a bug in the Linux NFS server to me. 
>> 
>> To me too... But this is caused by an obviously intentional and
>> even commented piece of code (see fs/nfsd/vfs.c:nfsd_vfs_write()).
>> I don't have any hope that this will be fixed in Linux, and while
>> I could fix the kernel on our server, this would get lost when
>> someone else (or myself after having forgot about the issue) installs
>> a kernel update.
>
> i think the behaviour is a common practice.
> it isn't appropriate to blame linux nfsd for it.

Especially because NetBSD's nfsd does the same thing; when I ran into
this a number of months ago (and then promptly forgot to open a PR), I
was able to reproduce it between two NetBSD 2.0.x systems.

-- 
(let ((C call-with-current-continuation)) (apply (lambda (x y) (x y)) (map
((lambda (r) ((C C) (lambda (s) (r (lambda l (apply (s s) l))))))  (lambda
(f) (lambda (l) (if (null? l) C (lambda (k) (display (car l)) ((f (cdr l))
(C k)))))))    '((#\J #\d #\D #\v #\s) (#\e #\space #\a #\i #\newline)))))