linux-kernel - Re: WARNING in perf_reg

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: <8ec677d7-f891-1c8b-33bd-16506974fafb@linux.intel.com>
Date:   Wed, 19 Jun 2019 17:15:32 -0400
From:   "Liang, Kan" <kan.liang@...ux.intel.com>
To:     Vince Weaver <vincent.weaver@...ne.edu>,
        syzbot <syzbot+10189b9b0f8c4664badd@...kaller.appspotmail.com>
Cc:     acme@...nel.org, acme@...hat.com,
        alexander.shishkin@...ux.intel.com, bp@...en8.de,
        eranian@...gle.com, hpa@...or.com, jolsa@...nel.org,
        jolsa@...hat.com, linux-kernel@...r.kernel.org, mingo@...nel.org,
        mingo@...hat.com, peterz@...radead.org,
        syzkaller-bugs@...glegroups.com, tglx@...utronix.de,
        torvalds@...ux-foundation.org, x86@...nel.org
Subject: Re: WARNING in perf_reg_value



On 6/19/2019 4:07 PM, Vince Weaver wrote:
> On Wed, 19 Jun 2019, syzbot wrote:
> 
>> syzbot found the following crash on:
>>
>> HEAD commit:    0011572c Merge branch 'for-5.2-fixes' of git://git.kernel...
>> git tree:       upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=12c38d66a00000
>> kernel config:  https://syzkaller.appspot.com/x/.config?x=fa9f7e1b6a8bb586
>> dashboard link: https://syzkaller.appspot.com/bug?extid=10189b9b0f8c4664badd
>> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
>> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1434b876a00000
>> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10e6c876a00000
> 
> the perf_fuzzer found this issue about a month ago, and patches were
> posted that fixed the issue (I've been unable to reproduce when running
> with a patched kernel).

Here are the patches posted.
https://lkml.org/lkml/2019/5/28/1022

Thanks,
Kan

> 
> Any reason they haven't been applied?
> 
> Vince
>