NetBSD Problem Report #57709

From www@netbsd.org  Sun Nov 19 22:05:31 2023
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id A54C61A9238
	for <gnats-bugs@gnats.NetBSD.org>; Sun, 19 Nov 2023 22:05:31 +0000 (UTC)
Message-Id: <20231119220530.511741A9239@mollari.NetBSD.org>
Date: Sun, 19 Nov 2023 22:05:30 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: uvm_grow cannot be dtraced with fbt
X-Send-Pr-Version: www-1.0

>Number:         57709
>Category:       kern
>Synopsis:       uvm_grow cannot be dtraced with fbt
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Nov 19 22:10:00 +0000 2023
>Originator:     Taylor R Campbell
>Release:        current
>Organization:
The NetBSD Stackgrowdation
>Environment:
>Description:
The function uvm_grow does not appear with fbt probes, entry or return, so it can't be dtraced as such.

Perhaps whatever problem is affecting uvm_grow might also affect other symbols in the kernel too.
>How-To-Repeat:
# dtrace -n 'fbt::uvm_grow:entry { @[stack()] = count() }'
dtrace: invalid probe specifier fbt::uvm_grow:entry { @[stack()] = count() }: probe description fbt::uvm_grow:entry does not match any probes
# dtrace -l -P fbt | grep uvm_grow
# 

>Fix:
Yes, please!

Home	PR Database Search