lkml.org 
[lkml]   [2002]   [Jul]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRE: [Linux-ia64] Linux kernel deadlock caused by spinlock bug
>>>>> On Mon, 29 Jul 2002 16:29:09 -0500, "Van Maren, Kevin" <kevin.vanmaren@unisys.com> said:

Van> Yes, but that isn't the point: unless you eliminate all rw
Van> locks, it is conceptually possible to cause a kernel deadlock
Van> by forcing contention on the locks you didn't remove, if the
Van> user can force the kernel to acquire a reader lock and if
Van> something else needs to acquire the writer lock. Correctness
Van> is the issue, not performance.

I agree with Kevin here. There must be some argument as to why
readers cannot indefinitely lock out a writer. A probabilistic
argument is fine, but just saying "contention doesn't happen"
certainly isn't good enough.

--david
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:27    [W:0.055 / U:0.248 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site