K 10
svn:author
V 6
alfred
K 8
svn:date
V 27
2004-09-05T22:24:28.000000Z
K 7
svn:log
V 389
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@

END