All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: syzbot <syzbot+6349a512c2938b2ad058@syzkaller.appspotmail.com>
Cc: andrea.parri@amarulasolutions.com, jpoimboe@redhat.com,
	linux-kernel@vger.kernel.org, luto@kernel.org, mingo@kernel.org,
	peterz@infradead.org, riel@surriel.com,
	syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org
Subject: Re: BUG: soft lockup in kvm_vm_release
Date: Sun, 24 Mar 2019 01:04:23 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.1903240058290.1798@nanos.tec.linutronix.de> (raw)
In-Reply-To: <000000000000958aa50584c851b7@google.com>

On Sat, 23 Mar 2019, syzbot wrote:

> syzbot has bisected this bug to:
> 
> commit 80eb865768703c0f85a0603762742ae1dedf21f0
> Author: Andrea Parri <andrea.parri@amarulasolutions.com>
> 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
code.

> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1362209b200000
> start commit:   57902dc0 Merge tag 'riscv-for-linus-5.0-rc7' of git://git...
> git tree:       upstream
> final crash:    https://syzkaller.appspot.com/x/report.txt?x=10e2209b200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1762209b200000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=ee434566c893c7b1
> dashboard link: https://syzkaller.appspot.com/bug?extid=6349a512c2938b2ad058
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14287e78c00000
> 
> Reported-by: syzbot+6349a512c2938b2ad058@syzkaller.appspotmail.com
> Fixes: 80eb86576870 ("sched/fair: Clean up comment in nohz_idle_balance()")
> 
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection

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.

Thanks,

	tglx




  reply	other threads:[~2019-03-24  0:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13 17:56 BUG: soft lockup in kvm_vm_release syzbot
2019-03-23 19:53 ` syzbot
2019-03-24  0:04   ` Thomas Gleixner [this message]
2019-03-26 10:11     ` Dmitry Vyukov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.1903240058290.1798@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=andrea.parri@amarulasolutions.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=riel@surriel.com \
    --cc=syzbot+6349a512c2938b2ad058@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.