NetBSD Problem Report #58169

From www@netbsd.org  Wed Apr 17 21:24:42 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))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 80E7D1A9238
	for <gnats-bugs@gnats.NetBSD.org>; Wed, 17 Apr 2024 21:24:42 +0000 (UTC)
Message-Id: <20240417212441.915D91A923A@mollari.NetBSD.org>
Date: Wed, 17 Apr 2024 21:24:41 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: tap(4) still uses IFF_OACTIVE and should stop
X-Send-Pr-Version: www-1.0

>Number:         58169
>Category:       kern
>Synopsis:       tap(4) still uses IFF_OACTIVE and should stop
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Apr 17 21:25:00 +0000 2024
>Originator:     Taylor R Campbell
>Release:        current, 10, 9, 8, ...
>Organization:
The TapIFF Oactivation
>Environment:
>Description:
tap(4) uses IFF_OACTIVE in struct ifnet::if_flags.
>How-To-Repeat:
code inspection for MP-safety
>Fix:
If tap(4) needs this state, it should be moved to tap_softc with access serialized by a tap-specific lock.

Home	PR Database Search