From 11cc4ab95aedee4f09e66649f0d59b167504faf6 Mon Sep 17 00:00:00 2001 From: Robert Watson Date: Sat, 19 Jan 2008 13:41:56 +0000 Subject: [PATCH] Use VOP_NULL rather than VOP_PANIC for Coda's vop_print routine, so as to avoid panicking in DDB show lockedvnods. MFC after: 3 days --- sys/fs/coda/coda_vnops.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sys/fs/coda/coda_vnops.c b/sys/fs/coda/coda_vnops.c index d28ff9aee510..2a9f65191561 100644 --- a/sys/fs/coda/coda_vnops.c +++ b/sys/fs/coda/coda_vnops.c @@ -132,7 +132,7 @@ struct vop_vector coda_vnodeops = { .vop_lock1 = coda_lock, /* lock */ .vop_unlock = coda_unlock, /* unlock */ .vop_bmap = coda_bmap, /* bmap */ - .vop_print = VOP_PANIC, /* print */ + .vop_print = VOP_NULL, /* print */ .vop_islocked = coda_islocked, /* islocked */ .vop_pathconf = coda_pathconf, /* pathconf */ .vop_advlock = VOP_NULL, /* advlock */