Date: Sat, 09 Dec 2023 22:09:46 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 275616] bwn driver causes kernel panic after connect Message-ID: <bug-275616-21060-387uwp95I3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275616-21060@https.bugs.freebsd.org/bugzilla/> References: <bug-275616-21060@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=3D275616 --- Comment #12 from Frank Hilgendorf <frank.hilgendorf@posteo.de> --- I repeated the test 5 times. The 5 reports first entry was always 'ieee80211_encap+0x512'. The bug seems to work deterministic. If it was kind of a race condition, where thread B frees the mbuf currently processed by thread A, I would expect multiple KASAN reports to start with different code lines because they should not be so exactly synchronized that thread B would always hit exactly the same point of execution of thread A. One more observation: Running the test with an unencrypted WLAN connection produces no KASAN repo= rt at all. --=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-275616-21060-387uwp95I3>