On Fri, Apr 12, 2019 at 2:33 PM Andy Lutomirski <luto@xxxxxxxxxx> wrote:
>
> Are you sure? I admit I'm not all that familiar with the innards of
> poll() on Linux, but I thought that the waitqueue only had to survive
> long enough to kick the polling thread and did *not* have to survive
> until poll() actually returned.
That is *not* true by default.
You can do that, but you need to make sure that your wakeup function
is one that removed itself from the wait queues. You can do that with
DEFINE_WAIT(name), which uses autoremove_wake_function(), or by using
your own auto-removing wakeup function together with
DEFINE_WAIT_FUNC() or init_waitqueue_func_entry().
But the default wake function does not remove on wakeup, and you'll
have to be around until poll() itself tears down all the tables.
In particular, the normal "poll_wait()" will use __pollwait, which does:
init_waitqueue_func_entry(&entry->wait, pollwake);
and pollwake() (which is thus what gets called at wake time) will not
remove anything from the wait queue.
So no, by default your wait queue has to stay around for the duration
of poll() (ie the duration of the file descriptor, since poll() gets a
reference to it).
You *can* play games with pollwait functions (and with wait functions
in general), but by default you should consider the wait function to
stay around.
Linus
