From 9e2aaec1e315cfabfbb080e57e983dc43e2f177d Mon Sep 17 00:00:00 2001 From: Jeff Roberson Date: Wed, 3 Aug 2005 05:02:08 +0000 Subject: [PATCH] - Use lockmgr_printinfo rather than rolling our own. This introduces a slight problem by using printf instead of db_printf however 'show lockedvnods' does the same so I believe it is ok for now. --- sys/kern/vfs_bio.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/sys/kern/vfs_bio.c b/sys/kern/vfs_bio.c index 59460629694..66cfa1e85ad 100644 --- a/sys/kern/vfs_bio.c +++ b/sys/kern/vfs_bio.c @@ -3762,9 +3762,6 @@ DB_SHOW_COMMAND(buffer, db_show_buffer) "b_bufobj = (%p), b_data = %p, b_blkno = %jd\n", bp->b_error, bp->b_bufsize, bp->b_bcount, bp->b_resid, bp->b_bufobj, bp->b_data, (intmax_t)bp->b_blkno); - db_printf("lockstatus = %d, excl count = %d, excl owner %p\n", - lockstatus(&bp->b_lock, NULL), bp->b_lock.lk_exclusivecount, - bp->b_lock.lk_lockholder); if (bp->b_npages) { int i; db_printf("b_npages = %d, pages(OBJ, IDX, PA): ", bp->b_npages); @@ -3778,6 +3775,7 @@ DB_SHOW_COMMAND(buffer, db_show_buffer) } db_printf("\n"); } + lockmgr_printinfo(&bp->b_lock); } DB_SHOW_COMMAND(lockedbufs, lockedbufs)