Page MenuHomeFreeBSD

hyperv/hn: Fixat RNDIS rxfilter after the successful RNDIS initialization
ClosedPublic

Authored by sepherosa_gmail.com on Apr 1 2017, 3:42 AM.
Tags
None
Referenced Files
Unknown Object (File)
Dec 17 2024, 12:05 PM
Unknown Object (File)
Dec 12 2024, 6:58 AM
Unknown Object (File)
Nov 17 2024, 12:58 PM
Unknown Object (File)
Nov 9 2024, 1:56 PM
Unknown Object (File)
Nov 8 2024, 8:01 PM
Unknown Object (File)
Sep 21 2024, 3:05 PM
Unknown Object (File)
Sep 21 2024, 8:18 AM
Unknown Object (File)
Sep 20 2024, 9:19 PM
Subscribers
None

Details

Summary

Under certain conditions on certain versions of Hyper-V, the RNDIS rxfilter is _not_ zero on the hypervisor side after the successful RNDIS initialization, which breaks the assumption of any following code (well, it breaks the RNDIS API contract actually). Clear the RNDIS rxfilter explicitly, drain packets sneaking through, and drain the interrupt taskqueues scheduled due to the stealth packets.

Reported-by: dexuan@

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

This revision was automatically updated to reflect the committed changes.