wakeup: Fix g_wakeup_acknowledge if signal comes in
It's not very likely, but there is a small chance that an incoming signal could disturb the non-blocking read calls in g_wakeup_acknowledge, leading to a subsequent spurious wake up.
This commit addresses the problem by doing the usual EINTR loop (which is already present on the write side incidentally)