From: syzbot <syzbot+338f014a98367a08a114@syzkaller.appspotmail.com>
To: bhumirks@gmail.com, coreteam@netfilter.org, davem@davemloft.net,
devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
johan.hedberg@gmail.com, kaber@trash.net,
kadlec@blackhole.kfki.hu, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
marcel@holtmann.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING: ODEBUG bug in cancel_delayed_work
Date: Sat, 01 Aug 2020 09:33:05 -0700 [thread overview]
Message-ID: <000000000000bf03f305abd37535@google.com> (raw)
In-Reply-To: <000000000000f298fc05abb42b70@google.com>
syzbot has bisected this issue to:
commit 43ff7f53de2294a83dcf84b35de6ffa1ffafae9d
Author: Bhumika Goyal <bhumirks@gmail.com>
Date: Thu Oct 6 18:10:01 2016 +0000
Staging: vc04_services: vchiq_arm: Remove unused function remote_event_destroy
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=107c810c900000
start commit: d8b9faec Merge tag 'drm-fixes-2020-07-31' of git://anongit..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=127c810c900000
console output: https://syzkaller.appspot.com/x/log.txt?x=147c810c900000
kernel config: https://syzkaller.appspot.com/x/.config?x=c0cfcf935bcc94d2
dashboard link: https://syzkaller.appspot.com/bug?extid=338f014a98367a08a114
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1111ad5c900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16565d5c900000
Reported-by: syzbot+338f014a98367a08a114@syzkaller.appspotmail.com
Fixes: 43ff7f53de22 ("Staging: vc04_services: vchiq_arm: Remove unused function remote_event_destroy")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-08-01 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 3:13 WARNING: ODEBUG bug in cancel_delayed_work syzbot
2020-08-01 16:33 ` 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=000000000000bf03f305abd37535@google.com \
--to=syzbot+338f014a98367a08a114@syzkaller.appspotmail.com \
--cc=bhumirks@gmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan.hedberg@gmail.com \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=syzkaller-bugs@googlegroups.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.