Date: Tue, 20 Nov 2018 09:46:35 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 230498] Fatal trap 12: page fault while in kernel mode in sysctl_dumpentry from sysctl NET_RT_DUMP Message-ID: <bug-230498-7501-UDAFn365q9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230498-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-230498-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=3D230498 Andrey V. Elsukov <ae@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #199345|0 |1 is obsolete| | --- Comment #8 from Andrey V. Elsukov <ae@FreeBSD.org> --- Created attachment 199372 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D199372&action= =3Dedit Proposed patch (for stable/12+) Sorry, but I think the panic is still possible. The kernel sets IFF_DYING f= lag too late, instead we can check for presence of IFF_UP. Also, do not reset to NULL ifp->if_addr pointer in the if_detach_internal(), this doesn't look li= ke very useful and also will protect us from NULL pointer dereference, when another thread will detach interface after we check IFF_UP flag. The access= ing to if_addr is safe in this case due to using epoch_call() in ifa_free(). --=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-230498-7501-UDAFn365q9>