From: syzbot <syzbot+eceab52db7c4b961e9d6@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: trying to register non-static key in ieee80211_do_stop
Date: Thu, 21 Jul 2022 09:46:14 -0700 [thread overview]
Message-ID: <000000000000afbe5805e45374a8@google.com> (raw)
In-Reply-To: <20220721162656.2033-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+eceab52db7c4b961e9d6@syzkaller.appspotmail.com
Tested on:
commit: e22c8879 Merge branch '100GbE' of git://git.kernel.org..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=119975d6080000
kernel config: https://syzkaller.appspot.com/x/.config?x=e37e9aaa4c062adb
dashboard link: https://syzkaller.appspot.com/bug?extid=eceab52db7c4b961e9d6
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=14583378080000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2022-07-21 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220721162656.2033-1-hdanton@sina.com>
2022-07-21 16:46 ` syzbot [this message]
[not found] <20220716045105.1420-1-hdanton@sina.com>
2022-07-16 5:07 ` [syzbot] INFO: trying to register non-static key in ieee80211_do_stop syzbot
[not found] <20220715225546.1354-1-hdanton@sina.com>
2022-07-15 23:06 ` syzbot
[not found] <20220715122619.1231-1-hdanton@sina.com>
2022-07-15 12:38 ` syzbot
[not found] <20220715114848.1124-1-hdanton@sina.com>
2022-07-15 11:59 ` syzbot
2022-07-14 12:08 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=000000000000afbe5805e45374a8@google.com \
--to=syzbot+eceab52db7c4b961e9d6@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@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).