Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: WARNING in perf_reg_value
To:     Vince Weaver <vincent.weaver@maine.edu>,
        syzbot <syzbot+10189b9b0f8c4664badd@syzkaller.appspotmail.com>
Cc:     acme@kernel.org, acme@redhat.com,
        alexander.shishkin@linux.intel.com, bp@alien8.de,
        eranian@google.com, hpa@zytor.com, jolsa@kernel.org,
        jolsa@redhat.com, linux-kernel@vger.kernel.org, mingo@kernel.org,
        mingo@redhat.com, peterz@infradead.org,
        syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
        torvalds@linux-foundation.org, x86@kernel.org
References: <000000000000734545058bb27ebb@google.com>
 <alpine.DEB.2.21.1906191605380.10498@macbook-air>
From:   "Liang, Kan" <kan.liang@linux.intel.com>
Message-ID: <8ec677d7-f891-1c8b-33bd-16506974fafb@linux.intel.com>
Date:   Wed, 19 Jun 2019 17:15:32 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.7.1
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.21.1906191605380.10498@macbook-air>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


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
>