linux-kernel - Re: WARNING in arch_install_hw

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]

Date:   Wed, 27 Mar 2019 14:28:05 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     syzbot <syzbot+370a6b0f11867bf13515@...kaller.appspotmail.com>
Cc:     frederic@...nel.org, gustavo@...eddedor.com, hpa@...or.com,
        linux-kernel@...r.kernel.org, mhiramat@...nel.org,
        mingo@...hat.com, syzkaller-bugs@...glegroups.com,
        tglx@...utronix.de, x86@...nel.org
Subject: Re: WARNING in arch_install_hw_breakpoint

On Sat, Mar 23, 2019 at 11:22:06PM -0700, syzbot wrote:
> Hello,
> 
> syzbot found the following crash on:
> 
> HEAD commit:    fd1f297b Merge tag 'drm-fixes-2019-03-22' of git://anongit..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1574f56d200000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=9a31fb246de2a622
> dashboard link: https://syzkaller.appspot.com/bug?extid=370a6b0f11867bf13515
> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1157b7cf200000
> 
> Bisection is inconclusive: the bug happens on the oldest tested release.
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=10ca39b3200000
> final crash:    https://syzkaller.appspot.com/x/report.txt?x=12ca39b3200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=14ca39b3200000

So I've tried running your .config in both an AMD and an Intel guest
like this:

./syz-execprog -repeat=0 repro.syz

and killed it after 30K executed programs without success in
reproducing.

Either I'm missing something and my environment doesn't match yours -
because looking at your console output it happens almost immediately
after starting - or it has been fixed in the meantime...

Hmmm.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.