[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Reauthentication EINTR bug
From: |
Roland McGrath |
Subject: |
Re: Reauthentication EINTR bug |
Date: |
Mon, 5 Jul 2010 13:23:15 -0700 (PDT) |
> This would be ideal, but my current understanding is that
> interrupt_operation() is mostly advisory and that the operation will
> restart or return EINTR regardless of what the server does, and if this
> is true then it is impossible to complete the RPC. However, my view of
> the interruption code is not consistent enough for me to be certain so
> I will investigate this possibility further.
I don't understand what you mean. There is a timeout of 1 second
(_hurdsig_interrupt_timeout) for pathologically broken servers that don't
reply to interrupt_operation. There is a timeout of 3 seconds
(_hurd_interrupted_rpc_timeout) for pathologically broken servers that
don't reply to operations in progress after an interrupt_operation RPC.
Those are failsafes for broken servers. It is certainly not the case that
interrupt_operation is "mostly advisory". All servers are obliged to reply
quickly to interrupt_operation and to make affected RPCs reply quickly.
Thanks,
Roland