When an rpc client is shut down, gss destroy messages are sent out asynchronously, and nobody waits for them. If those rpc messages arrive after the client is completely shut down, I assume they just get dropped by the networking code? Is it possible for them to arrive while we're still in the process of shutting down, and if so, what makes this safe? Olga's seeing some odd oopses on shutdown after testing our gss callback code. And of course it's probably our callback patches at fault, but I was starting to wonder if there was a problem with those destroy messages arriving at the wrong moment. Any pointers welcomed. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
