From 9d3fb6714181f44300a0a5431279841427e4ef06 Mon Sep 17 00:00:00 2001
From: rtm <rtm>
Date: Fri, 21 Jul 2006 22:10:40 +0000
Subject: namei

---
 Notes | 18 +++++++++++++++---
 1 file changed, 15 insertions(+), 3 deletions(-)

(limited to 'Notes')

diff --git a/Notes b/Notes
index 681d69a..f0955b8 100644
--- a/Notes
+++ b/Notes
@@ -142,10 +142,22 @@ systematic way to test sleep races?
 
 do you have to be holding the mutex in order to call wakeup()?
 
-should lock around printf, not putc
-
 device interrupts don't clear FL_IF
   so a recursive timer interrupt is possible
 
-the sleep/swtch/schedule code that holds over a lock is ugly
+what does inode->busy mean?
+  might be held across disk reads
+  no-one is allowed to do anything to the inode
+  protected by inode_table_lock
+inode->count counts in-memory pointers to the struct
+  prevents inode[] element from being re-used
+  protected by inode_table_lock
+
+blocks and inodes have ad-hoc sleep-locks
+  provide a single mechanism?
+
+need to lock bufs in bio between bread and brelse
 
+test 14-character file names
+and file arguments longer than 14
+and directories longer than one sector
-- 
cgit v1.2.3