From: syzbot <syzbot+10189b9b0f8c4664badd@syzkaller.appspotmail.com>
To: acme@kernel.org, acme@redhat.com,
alexander.shishkin@linux.intel.com, arvid.brodin@alten.se,
bp@alien8.de, davem@davemloft.net, eranian@google.com,
hpa@zytor.com, jolsa@kernel.org, jolsa@redhat.com,
kan.liang@linux.intel.com, linux-kernel@vger.kernel.org,
mingo@kernel.org, mingo@redhat.com, netdev@vger.kernel.org,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, torvalds@linux-foundation.org,
vincent.weaver@maine.edu, x86@kernel.org,
xiyou.wangcong@gmail.com
Subject: Re: WARNING in perf_reg_value
Date: Sat, 07 Dec 2019 21:03:00 -0800 [thread overview]
Message-ID: <0000000000006c96bd05992a318e@google.com> (raw)
In-Reply-To: <000000000000734545058bb27ebb@google.com>
syzbot suspects this bug was fixed by commit:
commit 311633b604063a8a5d3fbc74d0565b42df721f68
Author: Cong Wang <xiyou.wangcong@gmail.com>
Date: Wed Jul 10 06:24:54 2019 +0000
hsr: switch ->dellink() to ->ndo_uninit()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13e241dae00000
start commit: e01e060f Merge tag 'platform-drivers-x86-v5.2-3' of git://..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=fa9f7e1b6a8bb586
dashboard link: https://syzkaller.appspot.com/bug?extid=10189b9b0f8c4664badd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16615caea00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14a222aea00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: hsr: switch ->dellink() to ->ndo_uninit()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-12-08 5:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 19:47 WARNING in perf_reg_value syzbot
2019-06-19 20:07 ` Vince Weaver
2019-06-19 21:15 ` Liang, Kan
2019-06-20 12:13 ` Peter Zijlstra
2019-12-08 5:03 ` syzbot [this message]
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=0000000000006c96bd05992a318e@google.com \
--to=syzbot+10189b9b0f8c4664badd@syzkaller.appspotmail.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=arvid.brodin@alten.se \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vincent.weaver@maine.edu \
--cc=x86@kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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.