IPC_M_PHONE_HUNGUP can go unnoticed by a connection fibril
|Reported by:||Jakub Jermář||Owned by:||Jakub Jermář|
|Blocker for:||Depends on:|
If a client hangs up the phone after it sends the first message in a multi-message request, the IPC_M_HUNGUP call will not be read by the server in its main loop. Since the IPC_M_HUNGUP is delivered exactly once and is the last message in each connection, a connection fibril which does not react to this message appropriately will wait indefinitely in the next async_wait_for_call().