Fix MHI driver kernel panic with bridged/LAN traffic #151
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MHI driver v1.3.8-r3 crashes when LAN cable is connected during active cellular data transfer. Root cause: aggressive
WARN_ON()calls flood kernel log when non-QMAP packets arrive via bridge/LAN, triggering system instability.Changes
driver/quectel_MHI/src/devices/mhi_netdev_quectel.cndev_to_mhi()- Prevent dereference when unexpected device pointers arrive from bridge stackThe rx_handler registration with NULL (for HyFi compatibility) remains unchanged. This fix handles the resulting edge cases without warnings.
Testing
Requires validation on RM520N-GL module with immortalwrt 25.12, cellular data active + LAN connected.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.