> My gut feeling is this is the problem from mal-functional driver, e.g. > xhci-hcd. We do our best to protect core kernel from it instead of do the > cleanup for it. Agree. My intention wasn't to fix mal-functional driver, but to give it a hint that it's doing something wrong. (In the xhci-hcd case the patch indirectly avoids the later use-after-free in driver, a nice side effect here)
I think the same what Linus meant with > I'm less interested in the xhci-hcd case - which I certainly *hope* is > fixed already? - than in "if this happens somewhere else". What about giving only a WARN_ONCE? Wouldn't hurt but notice developers and ease bug hunting. Would be fine for me too. Finally, i also could put the patch in a private branch named "useful_patches" ;-) but then the community won't benefit. > > So my suggestion is to look into why xhci-hcd behave like this and fix that. > xhci-hcd fix proposal @ Hans de Goede already. Best regards Carsten
