summaryrefslogtreecommitdiffstats
path: root/lib/libpthread/thread/thr_cond.c
diff options
context:
space:
mode:
authorpeter <peter@FreeBSD.org>1998-11-06 15:16:07 +0000
committerpeter <peter@FreeBSD.org>1998-11-06 15:16:07 +0000
commitb5f83c161eae3fd27e934fe40a00f9f32869b1f9 (patch)
tree20926f39199ce68c7583c563deea7f21e9b29d10 /lib/libpthread/thread/thr_cond.c
parentd620d61682ae13ad87adef81b40487e5949ed660 (diff)
downloadFreeBSD-src-b5f83c161eae3fd27e934fe40a00f9f32869b1f9.zip
FreeBSD-src-b5f83c161eae3fd27e934fe40a00f9f32869b1f9.tar.gz
Don't put aggregate structs 4K large on the kernel stack, especially when
we can recurse when loading dependencies and that the kstack is limited to something like 6 or 7KB. Having a single dependency caused an instant double panic, and I stronly suspect some of the other strange "events" that I have seen are possibly as a result of taking a couple of interrupts with a large chunk of the stack already in use. While here, fix a minor logic hiccup in a sanity check.
Diffstat (limited to 'lib/libpthread/thread/thr_cond.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud