Edit: Does that last "ok" line mean that two other committers reviewed and OK'ed this patch as well? Three openbsd committers approved a one-line change that didn't fix a single thing? (And people wonder how the OpenSSL bug could live on for two years =) )
http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libssl/ssl/Mak...
I'll just leave this here. http://article.gmane.org/gmane.os.openbsd.misc/211963
Essentially the code mistakenly relies on the freelist being LIFO and not being scrubbed.
By all means, call the code what you want, but separate that from the people.
(I'm not endorsing anyone's behavior here, just pointing out how low the right hand side of modern American politics has degenerated, to provide some perspective.)
However, the freelist code somehow fails to follow this convention.
The performance is significantly better, and there is a much smaller danger of running out of space due to fragmentation issues.
What matters is not to always be right, but how you correct errors.
In my opinion, heartbleed is a counterexample to your point. It's a case where making the mistake at all caused a lot of damage, no matter how quickly they patched it.