Internal On Fri, 30 Oct 2026 08:35:55 +0100 Aurelien Jarno <[email protected]> wrote:
> Thanks for the bug report and the reproducer. This corresponds to > upstream bug BZ#27458, which already got a fixed in master: > https://sourceware.org/bugzilla/show_bug.cgi?id=27458 Thanks, haven’t found that, but it reads like this is the exact issue we’re seeing. > The bug was opened for for more than 5 years until someone reported a > similar issue using WSL2. I noticed that you also use WSL2. I am not > sure if it is a coincidence or if there is some application on WSL2 that > is affected by this bug. We’re using WSL2 only for development purposes, so it is a lucky coincidence that it matches with the other reporter(s). The reproducer also fails on native systems like arm64 or x86_64, so it’s not a WSL2 specific issue. > Do you mind providing a bit more details on how you found this bug and > what are the consequences, it might also help to decide if this bug > needs to be fixed in trixie or not, as it is technically not a > regression from bookworm or even bullseye. The bug was found by unit tests bound to a mutex wrapper layer in our code base. As this wrapper is totally under our control, it’s easy for us to apply a workaround in a central place: - Replace the affected pthread_mutex_trylock() call with e.g. pthread_mutex_clocklock() waiting on an already expired timeout. So after all, from my pov, we are good with the workaround and happy when a proper fix appears per upstream path for the next Debian major version. Thanks so far for your help! Mit freundlichen Grüßen / Kind regards i. A. Tobias Schülein Team Leader OS RT System R&D ASF KUKA Deutschland GmbH Zugspitzstraße 140, 86165 Augsburg / Germany www.kuka.com<http://www.kuka.com/> [email protected]<mailto:[email protected]> T +49 821 797‑3925 KUKA Deutschland GmbH Board of Directors: Michael Jürgens (Chairman), Johan Naten, Hui Zhang Registered Office: Augsburg HRB 14914 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of contents of this e-mail is strictly forbidden. Please consider the environment before printing this e-mail.
