clock_nanosleep failure

[Andreas Schwab]

On Jun 06 2017, "Dmitry V. Levin" <ldv at altlinux.org> wrote:

> Why clock_nanosleep is restarted after being interrupted by a signal
> handler?  What kind of kernel is behaving this way?

Indeed, this was a kernel bug.

Thanks, Andreas.

-- 
Andreas Schwab, schwab at linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."