From: syzbot <syzbot+de9526ade17c659d8336@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: rcu detected stall in __hrtimer_run_queues
Date: Sun, 31 Jul 2022 01:19:13 -0700 [thread overview]
Message-ID: <000000000000da754205e51589e3@google.com> (raw)
In-Reply-To: <20220731080330.602-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in __cfg80211_ibss_joined
------------[ cut here ]------------
WARNING: CPU: 1 PID: 6061 at net/wireless/ibss.c:36 __cfg80211_ibss_joined+0x487/0x520 net/wireless/ibss.c:36
Modules linked in:
CPU: 1 PID: 6061 Comm: kworker/u4:6 Not tainted 5.11.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Workqueue: cfg80211 cfg80211_event_work
RIP: 0010:__cfg80211_ibss_joined+0x487/0x520 net/wireless/ibss.c:36
Code: 0f 0b e9 0c fe ff ff e8 a7 19 75 f9 e9 41 fc ff ff e8 7d 19 75 f9 e9 7d fc ff ff e8 93 19 75 f9 e9 0d ff ff ff e8 99 51 32 f9 <0f> 0b e9 7e fc ff ff e8 8d 51 32 f9 0f 0b e8 86 19 75 f9 e9 e4 fb
RSP: 0018:ffffc90001d5fbd8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff888027c24bd0 RCX: 0000000000000000
RDX: ffff8880285e5340 RSI: ffffffff88408237 RDI: 0000000000000000
RBP: ffff888027c24000 R08: 0000000000000001 R09: ffffffff8ee66807
R10: fffffbfff1dccd00 R11: 0000000000000000 R12: 1ffff920003abf7d
R13: ffff88801486a718 R14: 0000000000000000 R15: 0000000000000006
FS: 0000000000000000(0000) GS:ffff8880b9f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000053edb8 CR3: 0000000025e9f000 CR4: 0000000000350ee0
Call Trace:
cfg80211_process_wdev_events+0x3de/0x5b0 net/wireless/util.c:977
cfg80211_process_rdev_events+0x6e/0x100 net/wireless/util.c:1003
cfg80211_event_work+0x1a/0x20 net/wireless/core.c:322
process_one_work+0x98d/0x15f0 kernel/workqueue.c:2275
worker_thread+0x64c/0x1120 kernel/workqueue.c:2421
kthread+0x3b1/0x4a0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296
Tested on:
commit: f40ddce8 Linux 5.11
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=12ecc26a080000
kernel config: https://syzkaller.appspot.com/x/.config?x=3565439810a4d2e5
dashboard link: https://syzkaller.appspot.com/bug?extid=de9526ade17c659d8336
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=171e281e080000
next parent reply other threads:[~2022-07-31 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220731080330.602-1-hdanton@sina.com>
2022-07-31 8:19 ` syzbot [this message]
[not found] <20220731110143.913-1-hdanton@sina.com>
2022-07-31 11:13 ` [syzbot] INFO: rcu detected stall in __hrtimer_run_queues syzbot
[not found] <20220731093631.791-1-hdanton@sina.com>
2022-07-31 9:53 ` syzbot
[not found] <20220731082711.724-1-hdanton@sina.com>
2022-07-31 8:47 ` syzbot
[not found] <20220731072530.451-1-hdanton@sina.com>
2022-07-31 7:38 ` syzbot
[not found] <20220327092631.4171-1-hdanton@sina.com>
2022-03-27 10:59 ` syzbot
2021-02-20 21:05 syzbot
2021-11-16 15:41 ` [syzbot] " syzbot
2021-11-16 15:42 ` Jens Axboe
2021-11-17 11:59 ` Paul E. McKenney
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=000000000000da754205e51589e3@google.com \
--to=syzbot+de9526ade17c659d8336@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.