> We know the WARN hits, we have the backtrace, and it is easy enough (in my setup > at least) to reproduce this. So, the WARN logic has done its job. > > Having more of these spam the kernel doesn't add much benefit I think. Well, this doesn't necessarily just catch a *single* issue, so it should remain for the future, I'd think. > Anyone have any suggestions on how to fix the underlying issue? I don't even have the backtrace and scenario that causes it. johannes
