NetBSD Problem Report #58500

From www@netbsd.org  Sun Jul 28 15:09:43 2024
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)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
	 client-signature RSA-PSS (2048 bits) client-digest SHA256)
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 75E9C1A9241
	for <gnats-bugs@gnats.NetBSD.org>; Sun, 28 Jul 2024 15:09:43 +0000 (UTC)
Message-Id: <20240728150942.1F8B51A9242@mollari.NetBSD.org>
Date: Sun, 28 Jul 2024 15:09:42 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: experimental wg(4) needs dtrace probes
X-Send-Pr-Version: www-1.0

>Number:         58500
>Category:       kern
>Synopsis:       experimental wg(4) needs dtrace probes
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jul 28 15:10:00 +0000 2024
>Originator:     Taylor R Campbell
>Release:        current, 10
>Organization:
The sdt:wg:netbsd:foundation
>Environment:
>Description:
The ad-hoc logging mechanism has been useful for debugging but it would be better to have systematic dtrace probes.

Probes should be available on all:

1. input handshake messages and processing results
2. output handshake messages and retries
3. state transitions
4. rekey decisions
5. data rx and processing results (decryption failure, replay detect, ...)
6. data tx and keepalives
7. task scheduling
8. task execution
9. wg_overudp_cb callbacks
10. socket upcalls and job
11. peer creation and destruction
12. anything else I haven't thought of
>How-To-Repeat:
try to diagnose wg(4) issues
>Fix:
Yes, please!

Home	PR Database Search