On 27 February 2021 01:10:23 EET, Thomas Munro <thomas.mu...@gmail.com> wrote: >Hello, > >Commit 82ebbeb0 added a workaround for (already in 2017) ancient Linux >kernels with no EPOLL_CLOEXEC. I don't see any such systems in the >build farm today (and if there is one hiding in there somewhere, it's >well past time to upgrade). I'd like to rip that code out, because >I'm about to commit some new code that uses another 2.6.17+ >XXX_CLOEXEC flag, and it'd be silly to have to write new workaround >code for that too, and a contradiction to have fallback code in one >place but not another. Any objections?
What happens if you try to try to compile or run on such an ancient kernel? Does it fall back to something else? Can you still make it work with different configure options? I'm just curious, not objecting. - Heikki
