Re: [patch 2/4] new timerfd API v2 - new timerfd API

One quick question:

> Like the previous timerfd API implementation, read(2) and poll(2) are supported
> (with the same interface).

Looking at that interface, it appears that a process doing a read() on a
timerfd with no timer set will block for a very long time.  It's an
obvious "don't do that" situation, but perhaps we could help an
occasional developer get a clue by returning something like -EINVAL when
the timer has not been set?

jon

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch 2/4] new timerfd API v2 - new timerfd API
    • From: Davide Libenzi <[email protected]>

• References:
  • [patch 2/4] new timerfd API v2 - new timerfd API
    • From: Davide Libenzi <[email protected]>

• Prev by Date: Re: [PATCH] Remove broken netfilter binary sysctls from bridging code
• Next by Date: Odd kprobes question...
• Previous by thread: Re: [patch 2/4] new timerfd API v2 - new timerfd API
• Next by thread: Re: [patch 2/4] new timerfd API v2 - new timerfd API
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]