summaryrefslogtreecommitdiff
path: root/Notes
diff options
context:
space:
mode:
authorrtm <rtm>2006-07-21 22:10:40 +0000
committerrtm <rtm>2006-07-21 22:10:40 +0000
commit9d3fb6714181f44300a0a5431279841427e4ef06 (patch)
treeb201602d7ff5e1a9ce51554bdf8c417f7caaa192 /Notes
parent11a9947f1a68e23001690955d8d0975ad4d6cf0c (diff)
downloadxv6-labs-9d3fb6714181f44300a0a5431279841427e4ef06.tar.gz
xv6-labs-9d3fb6714181f44300a0a5431279841427e4ef06.tar.bz2
xv6-labs-9d3fb6714181f44300a0a5431279841427e4ef06.zip
namei
Diffstat (limited to 'Notes')
-rw-r--r--Notes18
1 files changed, 15 insertions, 3 deletions
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