From: syzbot <syzbot+e28037ac1c96d2a86e89@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, benjamin.gaignard@linaro.org,
cmetcalf@ezchip.com, daniel.vetter@ffwll.ch,
daniel.vetter@intel.com, davem@davemloft.net,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, paulmck@linux.vnet.ibm.com,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, vincent.abriou@st.com,
yoshfuji@linux-ipv6.org
Subject: Re: WARNING: refcount bug in igmp_start_timer
Date: Thu, 11 Apr 2019 23:44:01 -0700 [thread overview]
Message-ID: <000000000000bfb6c405864fa081@google.com> (raw)
In-Reply-To: <0000000000002b42040573b8495a@google.com>
syzbot has bisected this bug to:
commit fc5e9d63a8db40e9e3a3b180be33d44af8a3cee8
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date: Wed May 24 14:52:05 2017 +0000
drm/sti: Drop drm_vblank_cleanup
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13f62c2d200000
start commit: ae596de1 Compiler Attributes: naked can be shared
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=100e2c2d200000
console output: https://syzkaller.appspot.com/x/log.txt?x=17f62c2d200000
kernel config: https://syzkaller.appspot.com/x/.config?x=5fa12be50bca08d8
dashboard link: https://syzkaller.appspot.com/bug?extid=e28037ac1c96d2a86e89
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=178537da400000
Reported-by: syzbot+e28037ac1c96d2a86e89@syzkaller.appspotmail.com
Fixes: fc5e9d63a8db ("drm/sti: Drop drm_vblank_cleanup")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-04-12 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-18 16:37 WARNING: refcount bug in igmp_start_timer syzbot
2018-09-20 20:06 ` syzbot
2019-04-12 6:44 ` syzbot [this message]
2019-11-09 14:32 ` syzbot
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=000000000000bfb6c405864fa081@google.com \
--to=syzbot+e28037ac1c96d2a86e89@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=benjamin.gaignard@linaro.org \
--cc=cmetcalf@ezchip.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=davem@davemloft.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vincent.abriou@st.com \
--cc=yoshfuji@linux-ipv6.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).