On Tue, Mar 18, 2008 at 06:15:15PM -0400, bfields wrote: > 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? In other words--when does the task that's created to send the destroy message get freed, and if that doesn't happen till after the rpc client and associated objects are freed, is there a risk of someone trying to access those objects through fields in that task? --b. > > 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
