Hello, Neil. On Mon, Aug 18, 2014 at 07:14:57AM +1000, NeilBrown wrote: > It does. The manage will even continue after there are no mounts active if > it is blocked on a non-responding server. > > If there is an outstanding RPC request to a non-responsive server > then the only way to abort that request is to send SIGKILL to the thread > which is waiting for the request. > So if we want things to clean up properly on shutdown it seems best for a > sigkill to be able to abort that thread. I see. I'm not convinced SIGKILL is the right way to communicate things like this tho. If this is actually a thing which needs to be exposed, we'd be a lot better off with an interface which is more to the point rather than meddling with signals to the manager kernel thread, which ultimately is an implementation detail. Given the requirement, I don't have objections to the patch but the requirement seems rather lopsided. Thanks. -- tejun -- 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
