summaryrefslogtreecommitdiffstats
path: root/sys/kern/kern_mac.c
diff options
context:
space:
mode:
authoralfred <alfred@FreeBSD.org>2004-09-05 22:24:28 +0000
committeralfred <alfred@FreeBSD.org>2004-09-05 22:24:28 +0000
commita91f58745724ed827c6e2ffbdf0be7b20c1ef29f (patch)
tree4bfa55cad48108d95d2fa94e4101de9d93c183f5 /sys/kern/kern_mac.c
parent4adf97c04d8b13231f16ad83651af84a422d145e (diff)
downloadFreeBSD-src-a91f58745724ed827c6e2ffbdf0be7b20c1ef29f.zip
FreeBSD-src-a91f58745724ed827c6e2ffbdf0be7b20c1ef29f.tar.gz
It's too easy to panic the machine when INVARIANTS are turned on
and you botch a call to nmount(2). This is because there is an INVARIANTS check that asserts that opt->len must be zero if opt->val is not NULL. The problem is that the code does not actually follow this invariant if there is an error while processing mount options. Fix the code to honor the INVARIANT. Silence on: fs@
Diffstat (limited to 'sys/kern/kern_mac.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud