NetBSD Problem Report #59182

From www@netbsd.org  Sun Mar 16 15:50:05 2025
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 E59D91A9239
	for <gnats-bugs@gnats.NetBSD.org>; Sun, 16 Mar 2025 15:50:04 +0000 (UTC)
Message-Id: <20250316155003.9C6B31A923E@mollari.NetBSD.org>
Date: Sun, 16 Mar 2025 15:50:03 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: ugen(4) should always attach with device-specific drivers as children
X-Send-Pr-Version: www-1.0

>Number:         59182
>Category:       kern
>Synopsis:       ugen(4) should always attach with device-specific drivers as children
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Mar 16 15:55:00 +0000 2025
>Originator:     Taylor R Campbell
>Release:        current, 10, 9, ...
>Organization:
The NetUSB Generation
>Environment:
>Description:
ugen(4) should always attach, with device-specific drivers attaching as children, so that userland can always do certain ugen(4) ioctls like getting device descriptors, and it should sprout a new ioctl command for userland to claim the device and kick out the kernel driver if needed.
>How-To-Repeat:
try to use tools like usbgen(8) from sysutils/usbutil to print the device descriptors of a USB device with a kernel driver, or generally try to get userland access to a device that has a kernel driver without rebooting
>Fix:
Yes, please!

Home	PR Database Search