lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 24 Mar 2019 01:04:23 +0100 (CET)
From:   Thomas Gleixner <>
To:     syzbot <>
Subject: Re: BUG: soft lockup in kvm_vm_release

On Sat, 23 Mar 2019, syzbot wrote:

> syzbot has bisected this bug to:
> commit 80eb865768703c0f85a0603762742ae1dedf21f0
> Author: Andrea Parri <>
> Date:   Tue Nov 27 11:01:10 2018 +0000
>    sched/fair: Clean up comment in nohz_idle_balance()

I.m pretty sure that this bisect is bogus. The commit changes a comment not

> bisection log:
> start commit:   57902dc0 Merge tag 'riscv-for-linus-5.0-rc7' of git://git...
> git tree:       upstream
> final crash:
> console output:
> kernel config:
> dashboard link:
> syz repro:
> Reported-by:
> Fixes: 80eb86576870 ("sched/fair: Clean up comment in nohz_idle_balance()")
> For information about bisection process see:

If I understand that correctly, then the bisect does not try to revert the
commit which it identified on top of the tree where it started to bisect.

I think that'd be a reasonably simple to do extra data point, at least when
the commit reverts cleanly on head.



Powered by blists - more mailing lists