On Fri, 16 Apr 2021 09:51:45 +0200 Dmitry Vyukov <dvyukov@xxxxxxxxxx> wrote: > > If you look at substantial base of bisection logs, you will find lots > of cases where bug types, functions don't match. Kernel crashes > differently even on the same revision. And obviously things change if > you change revisions. Also if you see presumably a different bug, what > does it say regarding the original bug. Yes, but there are also several types of cases where the issue will be the same. Namely lockdep. I agree that use after free warnings can have a side effect, and may be more difficult. But there's many other bugs that remain consistent across kernels. And if you stumble on one of them, look for it only. And if you hit another bug, and if it doesn't crash, then ignore it (of course this could be an issue if you have panic on warning set). But otherwise, just skip it. > > I would very much like to improve automatic bisection quality, but it > does not look trivial at all. > > Some random examples where, say, your hypothesis of WARN-to-WARN, > BUG-to-BUG does not hold even on the same kernel revision (add to this At least lockdep to lockdep, as when I do manual bisects, that's exactly what I look for, and ignore all other warnings. And that has found the problem commit pretty much every time. > different revisions and the fact that a different bug does not give > info regarding the original bug): > Can you tell me that all these examples bisected to the commit that caused the bug? Because if it did not, then you may have just proved my point ;-) > run #0: crashed: KASAN: use-after-free Read in fuse_dev_do_read > run #1: crashed: WARNING in request_end > run #2: crashed: KASAN: use-after-free Read in fuse_dev_do_read > run #3: OK > run #4: OK > [..] -- Steve
