Date: Thu, 25 Apr 2019 12:44:29 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 233955] [panic] Page fault in in6_purgeaddr (triggered by net/wireguard) Message-ID: <bug-233955-7501-J342F2OnMA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-233955-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-233955-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233955 --- Comment #31 from commit-hook@freebsd.org --- A commit references this bug: Author: kevans Date: Thu Apr 25 12:44:08 UTC 2019 New revision: 346670 URL: https://svnweb.freebsd.org/changeset/base/346670 Log: tun/tap: close race between destroy/ioctl handler It seems that there should be a better way to handle this, but this seems= to be the more common approach and it should likely get replaced in all of t= he places it happens... Basically, thread 1 is in the process of destroying = the tun/tap while thread 2 is executing one of the ioctls that requires the tun/tap mutex and the mutex is destroyed before the ioctl handler can acquire it. This is only one of the races described/found in PR 233955. PR: 233955 Reviewed by: ae MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D20027 Changes: head/sys/net/if_tap.c head/sys/net/if_tun.c --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-233955-7501-J342F2OnMA>