summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdlib/getenv.c
diff options
context:
space:
mode:
authorkib <kib@FreeBSD.org>2007-09-12 16:31:32 +0000
committerkib <kib@FreeBSD.org>2007-09-12 16:31:32 +0000
commite651705b7e9100bab6eada7793ec8c47c24d65aa (patch)
tree9af9fa02ecb42b6b92fe2fefa1fb1be0c3c57232 /lib/libc/stdlib/getenv.c
parentea3192c3f4d2f82afb6215fb244df50276cd3558 (diff)
downloadFreeBSD-src-e651705b7e9100bab6eada7793ec8c47c24d65aa.zip
FreeBSD-src-e651705b7e9100bab6eada7793ec8c47c24d65aa.tar.gz
When restoring the mount after umount failed, the MNTK_UNMOUNT flag
prevents insmntque() from placing reallocated syncer vnode on mount list, that causes panic in vfs_allocate_syncvnode(). Introduce MNTK_NOINSMNTQ flag, that marks the period when instmntque is not allowed to success, instead of MNTK_UNMOUNT. The MNTK_NOINSMNTQ is set and cleared simultaneously with MNTK_UNMOUNT, except on umount error path, where it is cleaned just before the syncer vnode is going to be allocated. Reported by: Peter Jeremy <peterjeremy optushome com au> Suggested by: tegge Approved by: re (rwatson)
Diffstat (limited to 'lib/libc/stdlib/getenv.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud