On Sun, Sep 20, Greg KH wrote: > Just use a lock, that's what it is there for.
How would that help? It might help because it enforces ordering. But that requires that all three utils get refactored to deal with the introduced locking. I will let KY comment on this. The issue I see with fcopy is that after or while fcopy_respond_to_host runs an interrupt triggers which also calls into hv_fcopy_onchannelcallback. It was most likely caused by a logic change in "recent" vmbus updates because this did not happen before. At least, the fcopy hang was not seen earler. Maybe the bug did just not trigger up to now for other reasons... Olaf -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
