From 4f74c87df8f3bd14ca2f13bb93dad2e5ec13b1bd Mon Sep 17 00:00:00 2001
From: Aaron Jacobs <jacobsa@google.com>
Date: Wed, 12 Aug 2015 12:40:31 +1000
Subject: [PATCH] Updated a redundant code walk.

---
 fuseops/ops.go | 13 ++-----------
 1 file changed, 2 insertions(+), 11 deletions(-)

diff --git a/fuseops/ops.go b/fuseops/ops.go
index f786474..5da1b5e 100644
--- a/fuseops/ops.go
+++ b/fuseops/ops.go
@@ -509,17 +509,8 @@ type ReadFileOp struct {
 //
 // Note that the kernel *will* ensure that writes are received and acknowledged
 // by the file system before sending a FlushFileOp when closing the file
-// descriptor to which they were written:
-//
-//  *  (http://goo.gl/PheZjf) fuse_flush calls write_inode_now, which appears
-//     to start a writeback in the background (it talks about a "flusher
-//     thread").
-//
-//  *  (http://goo.gl/1IiepM) fuse_flush then calls fuse_sync_writes, which
-//     "[waits] for all pending writepages on the inode to finish".
-//
-//  *  (http://goo.gl/zzvxWv) Only then does fuse_flush finally send the
-//     flush request.
+// descriptor to which they were written. Cf. the notes on
+// fuse.MountConfig.DisableWritebackCaching.
 //
 // (See also http://goo.gl/ocdTdM, fuse-devel thread "Fuse guarantees on
 // concurrent requests".)