summaryrefslogtreecommitdiffstats
path: root/sys/kern/kern_exec.c
diff options
context:
space:
mode:
authorphk <phk@FreeBSD.org>2002-10-11 20:52:44 +0000
committerphk <phk@FreeBSD.org>2002-10-11 20:52:44 +0000
commit1a10e2f35a4be7790f519238f8b6491bea83d6f2 (patch)
tree5da35adbd137bda54d9e4de2dde95118045aec76 /sys/kern/kern_exec.c
parent109f9bf9eb5b194938817ea5d4e9aca09eea9e51 (diff)
downloadFreeBSD-src-1a10e2f35a4be7790f519238f8b6491bea83d6f2.zip
FreeBSD-src-1a10e2f35a4be7790f519238f8b6491bea83d6f2.tar.gz
The CAM system has it's own ideas of what locks are to be held by whom.
So do GEOM. Not a pretty sight. Take all the interesting stuff out of GEOM::disk_create(), and leave just the creation of the fake dev_t. Schedule the topology munging to happen in the g_event thread with g_call_me(). This makes disk_create() pretty lock-agnostic, almost lock-atheist. Tripped over by: peter Sponsored by: DARPA & NAI Labs
Diffstat (limited to 'sys/kern/kern_exec.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud