This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/770] possible deadlock on double-free logging


------- Additional Comments From bugzilla at tree dot tlrmx dot org  2010-06-01 18:34 -------
I'd say rather, conservative. For me this is a bug which caused a big clustered
production (revenue generating) system to grind to a halt, often at inopportune
moments. To prove the assertion "somehow this bug has magically gone away
without any action" I have to risk every member of technical staff being woken
in the middle of the night as the app deadlocks suddenly and monitoring systems
start sending alerts. To even prepare for such an escapade might be a week's work.

So I don't want to do that. If the bug is gone, there'll be a patch that fixed
it. I can justify testing such a patch. If there isn't a patch, the bug is just
hiding and this bug report should remain open.

I can confirm (if it's any help) that the testcase supplied by Jakub Bogusz
doesn't deadlock on a modern glibc. But there could be lots of reasons for that.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=770

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]