[TLDR: This mail in primarily relevant for Linux kernel regression tracking. See link in footer if these mails annoy you.] On 13.02.23 04:38, Winter wrote: > Hi all, > > I'm facing the same issue as https://lore.kernel.org/stable/CAFsF8vL4CGFzWMb38_XviiEgxoKX0GYup=JiUFXUOmagdk9CRg@xxxxxxxxxxxxxx/, but on 5.15. I've bisected it across releases to 5.15.88, and can reproduce on 5.15.93. > > However, I cannot seem to find the identified problematic commit in the 5.15 branch, so I'm unsure if this is a different issue or not. > > There's a few ways to reproduce this issue, but the one I've been using is running libuv's (https://github.com/libuv/libuv) tests, specifically tests 271 and 277. > > #regzbot introduced v5.15.88.. #regzbot fix: fdaf88531cfd17b #regzbot ignore-activity Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you.
