Konstantin Belousov e30cf87ba1 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
2008-02-26 12:16:35 +00:00
..
2008-02-12 20:11:54 +00:00
2007-11-15 14:16:20 +00:00
2008-02-17 02:46:54 +00:00
2007-12-17 08:09:37 +00:00
2007-04-23 12:53:00 +00:00
2007-12-14 21:30:51 +00:00
2008-01-02 17:09:15 +00:00
2008-02-12 20:11:54 +00:00
2008-02-12 20:11:54 +00:00
2008-02-04 12:25:13 +00:00
2008-02-04 12:25:13 +00:00