linux-kernel - Re: [syzbot] possible deadlock in del

lists.openwall.net		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 linux-hardening linux-cve-announce 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]

Message-ID: <20210413134314.16068eeb@gandalf.local.home>
Date:   Tue, 13 Apr 2021 13:43:14 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     syzbot <syzbot+61e04e51b7ac86930589@...kaller.appspotmail.com>
Cc:     akpm@...ux-foundation.org, axboe@...nel.dk, bp@...en8.de,
        hpa@...or.com, jmattson@...gle.com, joro@...tes.org,
        kvm@...r.kernel.org, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org, mark.rutland@....com,
        masahiroy@...nel.org, mingo@...hat.com, pbonzini@...hat.com,
        peterz@...radead.org, rafael.j.wysocki@...el.com,
        seanjc@...gle.com, syzkaller-bugs@...glegroups.com,
        tglx@...utronix.de, vkuznets@...hat.com, wanpengli@...cent.com,
        will@...nel.org, x86@...nel.org
Subject: Re: [syzbot] possible deadlock in del_gendisk

On Tue, 13 Apr 2021 13:41:47 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:

> As the below splats look like it has nothing to do with this patch, and
> this patch will add a WARN() if there's broken logic somewhere, I bet the
> bisect got confused (if it is automated and does a panic_on_warning),
> because it will panic for broken code that his patch detects.
> 
> That is, the bisect was confused because it was triggering on two different
> issues. One that triggered the reported splat below, and another that this
> commit detects and warns on.

Is it possible to update the the bisect to make sure that if it is failing
on warnings, to make sure the warnings are somewhat related, before decided
that its the same bug?

-- Steve