Actions
Feature #6209
closedlibc mutexes break kernel writers hearts
Start date:
2015-09-08
Due date:
% Done:
100%
Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:
Description
Userland mutexes are a bit unfortunate. By default they don't check for errors at all and even if you do enable error checking mutexes, you have to wrap everything up in VERIFY0's. Instead, we should take a leaf from the kernel and add two private symbols to libc, mutex_enter() and mutex_exit() that behave identically to their kernel compatriots. Importantly these return void, they require error checking mutexes and if we don't have what we expect, we'll explicitly panic; i.e., abort().
Related issues
Updated by Electric Monk almost 7 years ago
- Status changed from New to Closed
git commit 0d045c0d0cb001d79480ee33be28514e847f8612
commit 0d045c0d0cb001d79480ee33be28514e847f8612 Author: Robert Mustacchi <rm@joyent.com> Date: 2015-09-14T20:47:46.000Z 6209 libc mutexes break kernel writers hearts Reviewed by: Jerry Jelinek <jerry.jelinek@joyent.com> Reviewed by: Josef 'Jeff' Sipek <jeffpc@josefsipek.net> Reviewed by: Dan McDonald <danmcd@omniti.com> Reviewed by: Garrett D'Amore <garrett@damore.org> Approved by: Dan McDonald <danmcd@omniti.com>
Updated by Andy Fiddaman 5 months ago
- Related to Bug #14521: bhyve should use error checking mutexes and check results added
Actions