summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdlib/bsearch.c
diff options
context:
space:
mode:
authornetchild <netchild@FreeBSD.org>2005-09-12 18:33:33 +0000
committernetchild <netchild@FreeBSD.org>2005-09-12 18:33:33 +0000
commit9986ff6dc192f2b7a031943daf01139ea74f4d1d (patch)
tree31195ae88d1b4049061078a3fa7b05207f81f4ea /lib/libc/stdlib/bsearch.c
parent491de3e2d267a2069dd39a8fdabdd3beb3135507 (diff)
downloadFreeBSD-src-9986ff6dc192f2b7a031943daf01139ea74f4d1d.zip
FreeBSD-src-9986ff6dc192f2b7a031943daf01139ea74f4d1d.tar.gz
- Fix the locking in dsp.c to prevent a LOR (AFAIK not on the LOR page).
- Remove an assertion in sound.c, it's not needed (and causes a panic now). From the conversation via mail between glebius and Ariff: ---snip--- > Well, but which mutex protects now? Do we own anything else > in pcm_chnalloc()? I see some queue(4) macros in pcm_chnalloc(), > they should be protected, shouldn't they? Queue insertion/removal occur during 1) driver loading (which is pretty much single thread / sequential) or unloading (mutex protected, bail out if there is any channel with refcount > 0 or busy). 2) vchan_create()/destroy(), (which is *sigh* quite complicated), but somehow protected by 'master'/parent channel mutex. Other thread cannot add/remove vchan (or even continue traversing that queue) unless it can acquire parent channel mutex. ---snip--- Fix the locking in dsp.c to prevent a LOR (AFAIK not on the LOR page). Submitted by: Ariff Abdullah <skywizard@MyBSD.org.my> Tested with: INVARIANTS[1] and DIAGNOSTICS[2] Tested by: netchild [1,2], David Reid <david@jetnet.co.uk> [1]
Diffstat (limited to 'lib/libc/stdlib/bsearch.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud