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: Fri, 15 Jul 2022 05:38:13 -0700 [thread overview]
Message-ID: <000000000000a6758405e3d74a5a@google.com> (raw)
In-Reply-To: <20220715122619.1231-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
SYZFATAL: executor failed NUM times: failed to create temp dir: mkdir ./syzkaller-testdir3ADDR: read-only file system
2022/07/15 12:37:03 SYZFATAL: executor failed 11 times: failed to create temp dir: mkdir ./syzkaller-testdir3040842611: read-only file system
Tested on:
commit: b11e5f6a net: sunhme: output link status with a single..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git
console output: https://syzkaller.appspot.com/x/log.txt?x=159f23b4080000
kernel config: https://syzkaller.appspot.com/x/.config?x=fa95f12403a2e0d2
dashboard link: https://syzkaller.appspot.com/bug?extid=eceab52db7c4b961e9d6
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=12cc29b4080000
next parent reply other threads:[~2022-07-15 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220715122619.1231-1-hdanton@sina.com>
2022-07-15 12:38 ` syzbot [this message]
[not found] <20220721162656.2033-1-hdanton@sina.com>
2022-07-21 16:46 ` [syzbot] INFO: trying to register non-static key in ieee80211_do_stop syzbot
[not found] <20220716045105.1420-1-hdanton@sina.com>
2022-07-16 5:07 ` syzbot
[not found] <20220715225546.1354-1-hdanton@sina.com>
2022-07-15 23:06 ` 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=000000000000a6758405e3d74a5a@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 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.