It seems that the rpc_shutdown_client logic grabs a clnt->cl_lock lock, and then in the rpc_exit logic it writes to the task->tk_action. But, I don't see anything keeping that from racing with the __rpc_execute() logic, which might also be modifying the task object without any locks held. Thanks, Ben -- Ben Greear <greearb@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.com -- 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
