4 ms·
Bit of a spoiler, but I did find this a fun followup worth skimming: > So the commit I had bisected to was the wrong one again – it exposed a latent bug simply
by rattray 3y ago
Bit of a spoiler, but I did find this a fun followup worth skimming:
> So the commit I had bisected to was the wrong one again – it exposed a latent bug simply because it ran the same code as a sleep.
The fix was by someone else, and is here: https://lore.kernel.org/stable/20230615091830.RxMV2xf_@linutronix.de/ https://lore.kernel.org/stable/20230615091830.RxMV2xf_@linut...
- mitko 3y agoIt is not that the commit was wrong. It was the right commit, in the sense that it did expose and trigger the bug. OP is being too modest :) But the root cause of the bug was in another earlier commit. In a complex system such as the linux kernel, there could be multiple contributing factors. Both the "introducing a sleep" and the "root bug" are contributing factors, but we as engineers tend to think of the "root bug" as the actual problem, because we like more elegant explanations. Also, the "root bug" is likely something that goes against the ethos of the software project, and "common sense best practices", to a much larger degree than "introducing a sleep" is.