summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdio/vsnprintf.c
diff options
context:
space:
mode:
authordavidxu <davidxu@FreeBSD.org>2012-03-18 00:22:29 +0000
committerdavidxu <davidxu@FreeBSD.org>2012-03-18 00:22:29 +0000
commit7218f7cbc7eab316c5db18cea6d60696090ba3df (patch)
tree6d96f7ec3dde4b33f4e5099c509d26aed5ab513c /lib/libc/stdio/vsnprintf.c
parent16846fb575f3587f475039b902dd766dbd540f2a (diff)
downloadFreeBSD-src-7218f7cbc7eab316c5db18cea6d60696090ba3df.zip
FreeBSD-src-7218f7cbc7eab316c5db18cea6d60696090ba3df.tar.gz
Some software think a mutex can be destroyed after it owned it, for
example, it uses a serialization point like following: pthread_mutex_lock(&mutex); pthread_mutex_unlock(&mutex); pthread_mutex_destroy(&muetx); They think a previous lock holder should have already left the mutex and is no longer referencing it, so they destroy it. To be maximum compatible with such code, we use IA64 version to unlock the mutex in kernel, remove the two steps unlocking code.
Diffstat (limited to 'lib/libc/stdio/vsnprintf.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud