nodefs: more doc

nodefs/README.md

@@ -86,5 +86,5 @@ or
 
    * Merge Fsync/FsyncDir?
 
-   * Merge Release/ReleaseDir?
+   * Merge Release/ReleaseDir? (others?)
  

nodefs/api.go

@@ -139,8 +139,6 @@ type Operations interface {
 	// ERANGE and the correct size.
 	ListXAttr(ctx context.Context, dest []byte) (uint32, fuse.Status)
 
-	// The methods below may be called on closed files, due to
-	// concurrency.
 	GetAttr(ctx context.Context, f FileHandle, out *fuse.AttrOut) fuse.Status
 
 	// Lookup should find a direct child of the node by child
@@ -284,8 +282,6 @@ type FileHandle interface {
 	// errors should happen in Flush instead.
 	Release() fuse.Status
 
-	// The methods below may be called on closed files, due to
-	// concurrency.
 	GetAttr(ctx context.Context, out *fuse.AttrOut) fuse.Status
 	Truncate(ctx context.Context, size uint64) fuse.Status
 	Chown(ctx context.Context, uid uint32, gid uint32) fuse.Status

nodefs/files.go

@@ -22,11 +22,10 @@ func newLoopbackFile(fd int) *loopbackFile {
 type loopbackFile struct {
 	fd int
 
-	// os.File is not threadsafe. Although fd themselves are
-	// constant during the lifetime of an open file, the OS may
-	// reuse the fd number after it is closed. When open races
-	// with another close, they may lead to confusion as which
-	// file gets written in the end.
+	// Although fd themselves are constant during the lifetime of
+	// an open file, the OS may reuse the fd number after it is
+	// closed. When open races with another close, they may lead
+	// to confusion as which file gets written in the end.
 	mu sync.Mutex
 }