Date: Wed, 16 Oct 2019 20:13:24 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 241106] tun/ppp: panic: vm_fault: fault on nofault entry when bringing ppp interface down Message-ID: <bug-241106-7501-xizMvfpn7e@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241106-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-241106-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=3D241106 lenzi.sergio@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lenzi.sergio@gmail.com --- Comment #4 from lenzi.sergio@gmail.com --- Created attachment 208370 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D208370&action= =3Dedit this patch test for null pointer in rtsock.c system panics on rtsock.c for the reason that rt->rt_ifp->if_addr have a nu= ll pointer.=20 It is not clear the reason rt->rt_ifp->if_addr have a null pointer but when= =20 try to access rt->rt_ifp->if_addr->ifa_addr near line 1578 of rtsock.c the system panics...=20 I also insert code of RTSOCK_LOCK/RTSOCK_UNLOCK on any ioctl call, and sin= ce than, the system does not panic any more.. A more study must be done where/why rt->rt_ifp->if_addr comes NULL, and in that case the colunm Netif from the command: netstat -4rn either shows "" (nothing) or "---". when this happens, the system panics some minutes later... --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241106-7501-xizMvfpn7e>