From: syzbot <syzbot+ca740b95a16399ceb9a5@syzkaller.appspotmail.com>
To: davem@davemloft.net, dvyukov@google.com,
hchunhui@mail.ustc.edu.cn, hdanton@sina.com, ja@ssi.bg,
jmorris@namei.org, johannes.berg@intel.com,
johannes@sipsolutions.net, kaber@trash.net, kuba@kernel.org,
kuznet@ms2.inr.ac.ru, kvalo@codeaurora.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, yoshfuji@linux-ipv6.org
Subject: Re: [syzbot] WARNING in hrtimer_forward
Date: Wed, 03 Nov 2021 02:21:06 -0700 [thread overview]
Message-ID: <00000000000002e72b05cfdeee4d@google.com> (raw)
In-Reply-To: <000000000000bd9ee505b01f60e2@google.com>
syzbot suspects this issue was fixed by commit:
commit 313bbd1990b6ddfdaa7da098d0c56b098a833572
Author: Johannes Berg <johannes.berg@intel.com>
Date: Wed Sep 15 09:29:37 2021 +0000
mac80211-hwsim: fix late beacon hrtimer handling
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=108b5712b00000
start commit: ba5f4cfeac77 bpf: Add comment to document BTF type PTR_TO_..
git tree: bpf-next
kernel config: https://syzkaller.appspot.com/x/.config?x=d44e1360b76d34dc
dashboard link: https://syzkaller.appspot.com/bug?extid=ca740b95a16399ceb9a5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1148fe4b900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12f5218d900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mac80211-hwsim: fix late beacon hrtimer handling
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2021-11-03 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000bd9ee505b01f60e2@google.com>
2021-11-03 9:21 ` syzbot [this message]
2021-12-04 10:19 ` [syzbot] WARNING in hrtimer_forward Dmitry Vyukov
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=00000000000002e72b05cfdeee4d@google.com \
--to=syzbot+ca740b95a16399ceb9a5@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=hchunhui@mail.ustc.edu.cn \
--cc=hdanton@sina.com \
--cc=ja@ssi.bg \
--cc=jmorris@namei.org \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kaber@trash.net \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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).