especially as testing each kernel revision when bisecting this regression can take a number of hours to verify whether the bug happens or not
I tried to track down an ext4 OOM lockup once and I never was able to get the correct load and memory usage, letting it run for over a month with very heavy disk and memory usage.. Only real live systems were able to let ext4 OOM and subsequently lock access to that partition.
So yeah, a few hours per bisect is not that high. But it does show how intense bug hunting can be.
Comment