On 17/03/2021 23:26, Stefan Metzmacher wrote: > Hi Pavel, > >>>> here're patches which fix linking of send[msg]()/recv[msg]() calls >>>> and make sure io_uring_enter() never generate a SIGPIPE. >> >> 1/2 breaks userspace. > > Can you explain that a bit please, how could some application ever > have a useful use of IOSQE_IO_LINK with these socket calls? Packet delivery of variable size, i.e. recv(max_size). Byte stream that consumes whatever you've got and links something (e.g. notification delivery, or poll). Not sure about netlink, but maybe. Or some "create a file via send" crap, or some made-up custom protocols >> Sounds like 2/2 might too, does it? > > Do you think any application really expects to get a SIGPIPE > when calling io_uring_enter()? If it was about what I think I would remove lots of old garbage :) I doubt it wasn't working well before, e.g. because of iowq, but who knows -- Pavel Begunkov
