On Mon, Dec 25, 2017 at 10:02:48PM +0000, Ben Hutchings wrote: > 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.
After two more weeks, I can now confirm that cherry-picking fb1522e099f0 onto earlier 4.13-rc kernels makes things _WORSE_. I believe that - plain 4.13-rc4 works fine and allows stable usage of KVM virtualization - 4.13-rc4 with cherry-picked fb1522e099f0 is bad, causing random segfaults and file-system corruption in VMs under disk and CPU load - 4.13-rc5 is bad either way I will start bisecting between 4.13-rc4 and 4.13-rc5, hoping that this will yield better results. Since I have to wait between three to five days to flag a kernel as "good" without too much doubt, and bisect 4.13-rc4..4.13-rc5 will take "roughly 7 steps". I am open to additional suggestions. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421