summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorantrik <antrik@users.sf.net>2011-03-16 03:14:36 +0100
committerantrik <antrik@users.sf.net>2011-03-25 23:32:10 +0100
commit70d256d2bd3fea95898383e7bcf6e90442cb6069 (patch)
treef82160599658892caaa9ccb54a1a8895970eb189
parent2462ca1a8be02689b5e0c5a13038472ad29a7888 (diff)
gsoc/ideas/diskfs_locking: Revert wording change
The new wording actually changes the meaning, to one which is wrong. The most frequent cause of Hurd hangs are probably ext2fs hangs; but they are *not* necessarily all caused by locking problems. (Actually most of them used to be caused by exec issues at some point... Though I'm not sure about the current situation.) Making it less diskfs-specific is probably useful though. This needs some further consideration.
-rw-r--r--community/gsoc/project_ideas/libdiskfs_locking.mdwn8
1 files changed, 2 insertions, 6 deletions
diff --git a/community/gsoc/project_ideas/libdiskfs_locking.mdwn b/community/gsoc/project_ideas/libdiskfs_locking.mdwn
index 0e38b6a0..74937389 100644
--- a/community/gsoc/project_ideas/libdiskfs_locking.mdwn
+++ b/community/gsoc/project_ideas/libdiskfs_locking.mdwn
@@ -11,12 +11,8 @@ License|/fdl]]."]]"""]]
[[!meta title="Fix libdiskfs Locking Issues"]]
-Every now and then, new locking issues are discovered in
-[[hurd/libdiskfs]] or [[hurd/translator/ext2fs]], for example. Nowadays
-these in fact seem to be the most often encountered cause of Hurd crashes
-/ lockups.
-
-One of these could be traced
+Nowadays the most often encountered cause of Hurd crashes seems to be lockups
+in the [[hurd/translator/ext2fs]] server. One of these could be traced
recently, and turned out to be a lock inside [[hurd/libdiskfs]] that was taken
and not released in some cases. There is reason to believe that there are more
faulty paths causing these lockups.