Alejandro Colomar <a...@kernel.org> writes: > Hi Sam, > > On Sat, Jun 21, 2025 at 04:57:32AM +0100, Sam James wrote: >> Alejandro Colomar <a...@kernel.org> writes: >> >> > [...] >> > >> > But the glibc maintainers mentioned that they're investigating about it >> > in distros, so I guess we'll eventually have the results of their >> > investigation. >> > >> >> To manage expectations: I haven't seen anyone say they're going to work >> on this. I recall Sid mentioning it *could* be done (not offering to do >> it) and Adhemerval made a similar remark, but I don't think anyone has >> said they're undertaking this work. >> >> If I've missed some other remark (very possible with the length of the >> thread!), let me know of course. > > Adhemerval mentioned in > Message-ID: <14fd8d0b-d32d-421f-8262-9c7ff9b1a...@linaro.org> > > | So what I would expect to move this forwards will be to.
The bit before that is important ;) That's where he said (and later corrected himself) that there was consensus, and so the next steps would be ... > | > | 1. Reopen https://sourceware.org/bugzilla/show_bug.cgi?id=12547 > | > | 2. Follow the suggestions laid out by Siddhesh [2]. The Distribution-wide > | verification seems already to be in progress, with some good results > | from gnulib realloc replacement and some work by you on checking some > | other projects (systemd for instance). > | > | 3. Prepare the patch to change it, along with the manual documentation, > | regression testcase, and the NEW entry. > | > | 4. Since we are near to 2.42 release, this change should be done once > | 2.43 starts to give some time to check potential issue with rolling > | distros like Fedora Rawhide. I don't think anybody is doing such distro-wide work other than things using gnulib where we'd notice if tests started to fail. That's what I'm trying to clarify: please don't wait on anybody doing it, because nobody's declared they're working on it.
