On Mon, 2017-12-25 at 14:15 +0100, Marc Haber wrote: [...] > I tried bisecting the kernel between 4.13 and 4.14, but the results are > inconclusive to me: > > - 569dbb88e80deb68974ef6fdd6a13edb9d686261 is good > - ddf720f86efe38cb3ef88b2eaad9ea8ad7c6f798 is bad > - ddf720f86efe38cb3ef88b2eaad9ea8ad7c6f798 was the result of the kernel > bisect between 4.13 and 4.14, but is a one-character typo fix in a > comment. > - I am also confused that ddf720f86efe38cb3ef88b2eaad9ea8ad7c6f798 is in > 4.13-rc7, therefore earlier than the "good" 4.13 relese [...]
It's on a branch that started at 4.13-rc7 but wasn't merged into mainline until after 4.13. Comparing the two of them, 569dbb88e80d has the addition of commit fb1522e099f0 "KVM: update to new mmu_notifier semantic v2". So I would guess that what you landed on is a different bug than the one you were looking for. Given that commit fb1522e099f0 was merged after -rc7 I assume it's an important fix, though the commit message doesn't spell that out. So I think that whenever bisect asks you to test a version that doesn't contain it, you should cherry-pick it first to avoid the other bug. (I think you will then need to use 'git bisect good|bad HEAD^' after testing, rather than implicitly flagging the current head commit.) Ben. -- Ben Hutchings The world is coming to an end. Please log off.
signature.asc
Description: This is a digitally signed message part
