https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275616
--- Comment #12 from Frank Hilgendorf <frank.hilgend...@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 report at all. -- You are receiving this mail because: You are the assignee for the bug.
