Date: Wed, 07 Nov 2018 19:10:49 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 219250] [Panic] panic: in6_ifattach_linklocal: ia == NULL (assigning ipv6 addresses) Message-ID: <bug-219250-7501-TicoHTsbHC@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219250-7501@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219250 Eric van Gyzen <vangyzen@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Affects Only Me |Affects Some People Summary|[Panic] [VIMAGE] panic: |[Panic] panic: |in6_ifattach_linklocal |in6_ifattach_linklocal: ia |(assigning ipv6 addresses |== NULL (assigning ipv6 |in vnet jail) |addresses) Hardware|amd64 |Any --- Comment #2 from Eric van Gyzen <vangyzen@FreeBSD.org> --- Something removed an IPv6 link-local interface address immediately after it was added. I don't know how this happened. However, it is clear that there is no thread synchronization to prevent this scenario and guarantee the assertion. This function (or its caller) really needs some kind of synchronization. Write-locking the if_addr_lock, which protects the interface's list of addresses, seems like a good choice, but I haven't tested that. I'm removing [VIMAGE] from the title, since this can be triggered without VIMAGE. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219250-7501-TicoHTsbHC>