From: syzbot <syzbot+35e70efb794757d7e175@syzkaller.appspotmail.com>
To: davem@davemloft.net, johan.hedberg@gmail.com,
johannes.berg@intel.com, johannes@sipsolutions.net,
kuba@kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
luciano.coelho@intel.com, marcel@holtmann.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in cancel_delayed_work
Date: Fri, 31 Jul 2020 01:44:05 -0700 [thread overview]
Message-ID: <000000000000a1816805abb8caa1@google.com> (raw)
In-Reply-To: <000000000000f6d80505abb42b60@google.com>
syzbot has bisected this issue to:
commit fbd05e4a6e82fd573d3aa79e284e424b8d78c149
Author: Luca Coelho <luciano.coelho@intel.com>
Date: Thu Sep 15 15:15:09 2016 +0000
cfg80211: add helper to find an IE that matches a byte-array
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1790af82900000
start commit: 83bdc727 random32: remove net_rand_state from the latent e..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1050af82900000
kernel config: https://syzkaller.appspot.com/x/.config?x=e59ee776d5aa8d55
dashboard link: https://syzkaller.appspot.com/bug?extid=35e70efb794757d7e175
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1160faa2900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11816098900000
Reported-by: syzbot+35e70efb794757d7e175@syzkaller.appspotmail.com
Fixes: fbd05e4a6e82 ("cfg80211: add helper to find an IE that matches a byte-array")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2020-07-31 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000f6d80505abb42b60@google.com>
2020-07-31 8:44 ` syzbot [this message]
2021-06-08 20:17 ` [syzbot] WARNING in cancel_delayed_work 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=000000000000a1816805abb8caa1@google.com \
--to=syzbot+35e70efb794757d7e175@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.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 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).