On Tue, 15 Jun 2021 20:22:53 -0500, Scott Cheloha wrote:
> After that is committed, I'm unclear whether alarm(3) can fail anymore
> on OpenBSD. The only remaining plausible failure case I can see is
> EFAULT. But I'm unsure if that's possible. Can we get an EFAULT if
> both arguments point to stack memory?
I don't think it is possible for alarm(3) to fail in this case.
The only way I see it failing is if the stack gets corrupted. I
think we can just initialize oitv to { 0 } and ignore the setitimer()
return value.
- todd
