NetBSD Problem Report #47117
From campbell@mumble.net Tue Oct 23 22:11:32 2012
Return-Path: <campbell@mumble.net>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
by www.NetBSD.org (Postfix) with ESMTP id 2EBDE63E398
for <gnats-bugs@gnats.NetBSD.org>; Tue, 23 Oct 2012 22:11:32 +0000 (UTC)
Message-Id: <20121023221053.A7EC2604BF@jupiter.mumble.net>
Date: Tue, 23 Oct 2012 22:10:53 +0000 (UTC)
From: Taylor R Campbell <campbell+netbsd@mumble.net>
Reply-To: Taylor R Campbell <campbell+netbsd@mumble.net>
To: gnats-bugs@gnats.NetBSD.org
Subject: lockstat output doesn't show caller of genfs_lock or vn_lock
X-Send-Pr-Version: 3.95
>Number: 47117
>Category: kern
>Synopsis: lockstat output doesn't show caller of genfs_lock or vn_lock
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Tue Oct 23 22:15:00 +0000 2012
>Originator: Taylor R Campbell <campbell+netbsd@mumble.net>
>Release: NetBSD 6.99.14
>Organization:
>Environment:
Architecture: any
Machine: any
>Description:
The vast majority of the rwlocks in lockstat output are vnode
locks, for which it only displays genfs_lock as the taker of
the lock. It might be nice if it were easier to see who wanted
the lock in order to get an idea of which operations the
contention lies in.
>How-To-Repeat:
Run lockstat while doing file system stuff. Fail to attain
enlightenment. Put on a sad face.
>Fix:
Yes, please!
(Contact us)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.