Re: [issue1942] non-zero exclusive count(Re: locking against
Ok, I think I fixed the non-zero exclusive count panic, please try
with the latest master (I pushed it).
It looks like a shared->exclusive upgrade can steal an exclusive lock
out from under an exclusive lock request. The exclusive lock request
uses two acquire() operations internally and the upgrade can slip in
inbetween them.
The recursive lock that my hold/drop patch addresses is still an issue.
The hold/drop patch fixes it but might have other problems (the buffer
can still be invalidated while hold). I'm still looking into that.
Please test.
-Matt
討論串 (同標題文章)
完整討論串 (本文為第 4 之 5 篇)：