On Sat, Feb 27, 2021 at 9:30 PM Thomas Munro wrote:
> On Sat, Feb 27, 2021 at 9:01 PM Heikki Linnakangas wrote:
> > 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 option
On Sat, Feb 27, 2021 at 9:01 PM Heikki Linnakangas wrote:
> On 27 February 2021 01:10:23 EET, Thomas Munro wrote:
> >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 o
On 27 February 2021 01:10:23 EET, Thomas Munro 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 upg
Thomas Munro writes:
> 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,
Sep 17 00:00:00 2001
From: Thomas Munro
Date: Sat, 27 Feb 2021 11:22:16 +1300
Subject: [PATCH] Remove latch.c workaround for Linux < 2.6.27.
Ancient Linux had no EPOLL_CLOEXEC flag, so commit 82ebbeb0 added a
separate code path with an fcntl() call. Kernels of that vintage are
long gone. Now se
