On 14/11/2019 05.49, Jens Axboe wrote: > On 11/13/19 9:31 PM, Jens Axboe wrote: >> This is a case of "I don't really know what I'm doing, but this works >> for me". Caveat emptor, but I'd love some input on this. >> >> I got a bug report that using the poll command with signalfd doesn't >> work for io_uring. The reporter also noted that it doesn't work with the >> aio poll implementation either. So I took a look at it. >> >> What happens is that the original task issues the poll request, we call >> ->poll() (which ends up with signalfd for this fd), and find that >> nothing is pending. Then we wait, and the poll is passed to async >> context. When the requested signal comes in, that worker is woken up, >> and proceeds to call ->poll() again, and signalfd unsurprisingly finds >> no signals pending, since it's the async worker calling it. >> >> That's obviously no good. The below allows you to pass in the task in >> the poll_table, and it does the right thing for me, signal is delivered >> and the correct mask is checked in signalfd_poll(). >> >> Similar patch for aio would be trivial, of course. > > From the probably-less-nasty category, Jann Horn helpfully pointed out > that it'd be easier if signalfd just looked at the task that originally > created the fd instead. That looks like the below, and works equally > well for the test case at hand. Eh, how should that work? If I create a signalfd() and fork(), the child's signalfd should only be concerned with signals sent to the child. Not to mention what happens after the parent dies and the child polls its fd. Or am I completely confused? Rasmus
