Date: Mon, 17 Mar 2025 16:44:12 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 283426] panic in sbappendaddr_locked() Message-ID: <bug-283426-7501-VTeUNFOYIZ@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=283426 Gleb Smirnoff <glebius@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|net@FreeBSD.org |wireless@FreeBSD.org --- Comment #4 from Gleb Smirnoff <glebius@FreeBSD.org> --- Dan Epure submitted similar panic to me, also FreeBSD 14.2-RELEASE. The backtrace is the same, the invalid mbuf without M_PKTHDR set is originating from iwm(4) driver. I'm 99% confident that bug is there and not in IP, UDP or socket buffer code. And indeed high change this is a regression from 14.1-RELEASE. -- 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-VTeUNFOYIZ>