Bug 219086
Summary: | mt76 driver: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 | ||
---|---|---|---|
Product: | Drivers | Reporter: | Michael (ZeroBeat) |
Component: | network-wireless | Assignee: | drivers_network-wireless (drivers_network-wireless) |
Status: | RESOLVED PATCH_ALREADY_AVAILABLE | ||
Severity: | high | CC: | regressions, ZeroBeat |
Priority: | P3 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | >= 6.9.5 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | 0d9c2beed116e623ac30810d382bd67163650f98 |
Description
Michael
2024-07-23 15:38:43 UTC
After some more tests, I'm not longer sure that the problem is caused by the commit mentioned. It looks like it is only a symptom. I tested several mt76 devices e.g. this one: D 148f:761a Ralink Technology, Corp. MT7610U ("Archer T2U" 2.4G+5G WLAN Adapter Driver is mt76x0u: $ hcxdumptool -l 0 3 503eaa1a736c f49da7d6f202 * wlp48s0f4u2u4 mt76x0u NETLINK All of them are running into the same problem as mentioned above, while other devices are working as expected, e.g.: ID 2357:010c TP-Link TL-WN722N v2/v3 [Realtek RTL8188EUS] Driver is rtl8xxxu $ hcxdumptool -l 0 3 9ca2f4094fe1 c8aacc8562e3 + wlp48s0f4u2u4 rtl8xxxu NETLINK This leads me to the assumption that the "chanctx emulation" inside the mt76 series driver caused the real problem. I'd like to forward your report by mail. Can I CC you? this would expose your email address to the public. Yes, you can add me to CC. The entire chanctx implementation is much more complex than expected. Good to be in CC if questions arise. This patch fixed it: https://patchwork.kernel.org/project/linux-wireless/patch/20240725184836.25d334157a8e.I02574086da2c5cf0e18264ce5807db6f14ffd9c0@changeid/ $ uname -r 6.10.0-1-git-12246-g786c8248dbd3-dirty $ sudo hcxdumptool -i wlp5s0f4u2 --rcascan=active ... ^C 24 Packet(s) captured by kernel 0 Packet(s) dropped by kernel 14 PROBERESPONSE(s) captured |