|Priority:||4 - Normal|
|Created by:||Former user|
|Reported by:||Former user|
|Assigned to:||Former user|
Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2017-07-24T15:23:39.000Z)
2017-08-03 WARSAW PACT (Release Date: 2017-08-03)
Several customers, internal and otherwise, have reported seeing nginx periodically spew errors related to epoll_wait yielding EPERM. This is a little bit odd, as there isn't much in the way of access checking in the guts of epoll/devpoll itself. That logic does, however, allow errors from VOP_POLL handlers to trickle up. With the merging of OS-5941, attempts to epoll on regular files and directories will result in EPERM.
Since epoll_wait = EPERM is the expectation if a normal file end up in the set, why then is nginx stumbling over the problem. Certainly it wouldn't add a plain fd intentionally, only to complain about it later. Another possibility does exist in this case: An active fd was closed, without first being removed from the set, followed by it being quickly reassigned when nginx went to open a regular file. This touches on one of the wrinkles in the core design of epoll: it expects to act on the underlying
struct file (our
vnode_t would likely be the closes analog) rather than the fd itself. This places a premium in detecting when the resource backing of an fd changes.
I believe the trouble detailed in illumos-joyent#139 is also related to this. In that case, it wasn't EPERM problems due to VREG resources sneaking into the set but rather unexpected successful events for freshly accept(2)ed sockets which occupy previously polled fd entries. The framework in question (https://github.com/oktal/pistache/) maintains a list of active sockets which it compares events against. When the accept(2) succeeds, placing a new resource into that fd, it's possible for the epoll_wait() to win the race against the framework socket registration code, emitting an event which won't match against the internal list of known sockets.
OS-6116 epoll should better detect fd reassignment
Reviewed by: Jerry Jelinek <email@example.com>
Reviewed by: Dan McDonald <firstname.lastname@example.org>
Reviewed by: Jason King <email@example.com>
Approved by: Jerry Jelinek <firstname.lastname@example.org>