Do not assert any locks for VOP_PRINT. In particular, do not assert that

the vnode interlock is not held. vn_printf() already correctly handles
locked and unlocked vnode interlocks, and all the in-tree vop_print
methods are interlock-agnostic.

Some code calls vprintf() with the vnode interlock held, that causes
unjustified panics with INVARIANTS (ffs_syncvnode() as example).

Reported by:	Peter Holm

1 files changed, 1 insertions, 1 deletions

diff --git a/sys/kern/vnode_if.src b/sys/kern/vnode_if.src
index 754cbc3..b06e64f 100644
--- a/sys/kern/vnode_if.src
+++ b/sys/kern/vnode_if.src
@@ -410,7 +410,7 @@ vop_getwritemount {
 };
 
 
-%% print	vp	= = =
+%% print	vp	- - -
 
 vop_print {
 	IN struct vnode *vp;