imago killed by io_uring?
Adrian Bunk <[email protected]> Tue, 5 Mar 2024 17:42:45 +0200
| Newsgroups | gmane.linux.debian.ports.alpha |
|---|---|
| Message-ID | <Zec9ddvCdl1AT3Im@localhost> |
Hi, liburing is Not-For-Us on Alpha since 2022, and if I saw it correctly imago was recently twice killed by bfs (which now uses io_uring). Recent kernels do contain io_uring fixes (e.g. in 5.10.186), which might or might not be related. Blacklisting liburing and packages build depending on it on imago might be a (not necessarily complete) short-term workaround, currently these would be: Reverse-Build-Depends ===================== * bfs (for liburing-dev) * ceph (for liburing-dev) * libdex (for liburing-dev) * mariadb (for liburing-dev) * mpd (for liburing-dev) * plocate (for liburing-dev) This is not necessarily a complete workaround since libdex and libmariadbd are linked with liburing, but it might be a short-term workaround. cu Adrian