On 06.07.23 10:08, Forza wrote: >>> On Wed, May 24, 2023 at 11:13:57AM +0200, David Sterba wrote: > [...] > A small update. Thx for this. > I have been able test 6.2.16, all 6.3.x and 6.4.1 and they all show > the same issue. > > I am now trying 6.1.37 since two days and have not been able to > reproduce this issue on any of my virtual qemu/kvm machines. Perhaps > this information is helpful in finding the root cause? That means it's most likely a regression between v6.1..v6.2 (or v6.1..v6.2.16 if we are unlucky) somewhere (from earlier in the thread it sounds like it might not be Btrfs). Which makes we wonder: how long do you usually need to reproduce the issue? If it's not too long it might mean that a bisection is the best way forward, unless some developer sits down and looks closely at the logs. With a bit of luck some dev will do that; but if we are unlucky we likely will need a bisection. 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 If I did something stupid, please tell me, as explained on that page.
