From cefdb4e540801e46476f5bc2ea4cf8e4bec784a8 Mon Sep 17 00:00:00 2001
From: Sage Weil <sage@newdream.net>
Date: Thu, 2 Oct 2008 09:57:48 -0700
Subject: [PATCH] todos

---
 src/TODO | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/src/TODO b/src/TODO
index 1ad622341b783..af100b6f818d6 100644
--- a/src/TODO
+++ b/src/TODO
@@ -44,17 +44,29 @@ kernel client
   - ... writeback vs ENOSPC vs flush vs close()... hrm...
 - set mapping bits for ENOSPC, EIO?
 - flush caps on sync, fsync, etc.
-  - do we need to block?
+  - do we need to block?  how do we track that?
 - forced unmount?
-- deal with CAP_RDCACHE properly: are we invalidating cache pages correctly?
 - procfs/debugfs
   - adjust granular debug levels too
     - should we be using debugfs?
   - a dir for each client instance (client###)?
   - hooks to get mds, osd, monmap epoch #s
+- populate sysfs?
+  - things that would be useful to see
+    - fsid
+    - map versions on client
+    - outstanding mds, osd, mon requests?
 - fix readdir vs fragment race by keeping a separate frag pos, and ignoring dentries below it
 - reconnect after being disconnected from the mds
 
+kclient items to review
+- fill_trace locking
+- async trunc
+- async writeback
+- cache invalidation race, locking problems
+  - cap changes are serialized by i_lock, but (thorough) cache invalidation may block..
+
+
 vfs issues
 - real_lookup() race:
   1- hash lookup find no dentry
-- 
2.39.5