* Re: Q. NFS, return value of close(2)
[not found] ` <1281546396.3262.7.camel@heimdal.trondhjem.org>
@ 2010-08-13 12:25 ` Milan Broz
0 siblings, 0 replies; only message in thread
From: Milan Broz @ 2010-08-13 12:25 UTC (permalink / raw)
To: Trond Myklebust; +Cc: J. R. Okajima, linux-fsdevel, Linux Kernel Mailing List
On 08/11/2010 07:06 PM, Trond Myklebust wrote:
>> commit e56f956a08a6227004cd9b7747df6a089dbb3594
>> Author: J. R. Okajima <hooanon05@yahoo.co.jp>
>> Date: Thu Aug 12 02:00:02 2010 +0900
>>
>> NFS: fix the return value of nfs_file_fsync()
>>
>> By the commit
>> af7fa16 2010-08-03 NFS: Fix up the fsync code
>> close(2) became returning the non-zero value even if it went well.
>> nfs_file_fsync() should return 0 when "status" is positive.
>>
>> Signed-off-by: J. R. Okajima <hooanon05@yahoo.co.jp>
Hi,
please can you send this patch to Linus' tree?
NFS is currently broken, so it will save time for people trying
to bisect the problem.
It breaks even elementary operation on nfs mounts
# cat a > b
cat: write error
Patch above from nfs-git fixed the problem for me
http://git.linux-nfs.org/?p=trondmy/nfs-2.6.git;a=commitdiff;h=0702099bd86c33c2dcdbd3963433a61f3f503901
Thanks,
Milan
--
mbroz@redhat.com
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-08-13 12:25 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <4387.1281540989@jrobl>
[not found] ` <1281544299.3262.2.camel@heimdal.trondhjem.org>
[not found] ` <7396.1281546264@jrobl>
[not found] ` <1281546396.3262.7.camel@heimdal.trondhjem.org>
2010-08-13 12:25 ` Q. NFS, return value of close(2) Milan Broz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox