From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: [PATCH 0/2] fix nfsd stable write implementation Date: Fri, 26 Oct 2012 17:06:55 -0400 Message-ID: <1351285617-20450-1-git-send-email-bfields@redhat.com> Cc: Peter Staubach , "J. Bruce Fields" To: linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Return-path: Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org From: "J. Bruce Fields" Peter pointed out to me that the nfs server is implementing stable writes by setting the O_SYNC flag. I can't see why we couldn't write and then sync instead, but I don't know this stuff as well as I should; does the following look reasonable to people? --b. J. Bruce Fields (2): nfsd: assume writeable exportabled filesystems have f_sync nfsd: use vfs_fsync_range(), not O_SYNC, for stable writes fs/nfsd/vfs.c | 26 ++++++-------------------- 1 file changed, 6 insertions(+), 20 deletions(-) -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html