Date: Tue, 01 Apr 2025 02:53:11 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 283426] panic in sbappendaddr_locked() - if_ovpn related? Message-ID: <bug-283426-7501-9AMMmL1fqs@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-283426-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-283426-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=3D283426 --- Comment #15 from takahiro.kurosawa@gmail.com --- Created attachment 259236 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D259236&action= =3Dedit testcase to reproduce the similar panic I've been able to reproduce a similar panic with the attached patch for /usr/tests/sys/net/if_ovpn/if_ovpn. The testcase uses a broadcast packet for the openvpn port that needs m_copym() calls to deliver it to each socket. m_copym() increases reference counts of mbuf clusters that results in m_unshare() returning a new mbuf and dropping M_PKTHDR of the original mbuf. To reproduce the panic: ---- cd /usr/tests/sys/net cp -pr if_ovpn if_ovpn.283426 cd if_ovpn.283426 patch -p1 < /path/to/repro-283426.diff kldload if_epair if_bridge if_ovpn sync; sync; sync kyua debug if_ovpn:bz283426 ---- --=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-283426-7501-9AMMmL1fqs>