From: syzbot <syzbot+69904c3b4a09e8fa2e1b@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: rcu detected stall in batadv_nc_worker (3)
Date: Sat, 15 Oct 2022 20:03:21 -0700 [thread overview]
Message-ID: <000000000000febc1605eb1e196f@google.com> (raw)
In-Reply-To: <20221016014012.519-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
INFO: rcu detected stall in corrupted
rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P4088 } 2636 jiffies s: 2445 root: 0x0/T
rcu: blocking rcu_node structures (internal RCU debug):
Tested on:
commit: 55be6084 Merge tag 'timers-core-2022-10-05' of git://g..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=12b0a464880000
kernel config: https://syzkaller.appspot.com/x/.config?x=df75278aabf0681a
dashboard link: https://syzkaller.appspot.com/bug?extid=69904c3b4a09e8fa2e1b
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=136f787c880000
next parent reply other threads:[~2022-10-16 3:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221016014012.519-1-hdanton@sina.com>
2022-10-16 3:03 ` syzbot [this message]
[not found] <20221018061633.890-1-hdanton@sina.com>
2022-10-18 18:58 ` [syzbot] INFO: rcu detected stall in batadv_nc_worker (3) syzbot
[not found] <20221017114136.796-1-hdanton@sina.com>
2022-10-18 1:41 ` syzbot
[not found] <20221016110248.708-1-hdanton@sina.com>
2022-10-16 12:42 ` syzbot
[not found] <20221016044826.637-1-hdanton@sina.com>
2022-10-16 12:27 ` syzbot
[not found] <20221015234821.438-1-hdanton@sina.com>
2022-10-16 0:13 ` syzbot
2020-10-01 10:35 syzbot
2022-10-15 19:01 ` [syzbot] " syzbot
2022-10-16 17:34 ` 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=000000000000febc1605eb1e196f@google.com \
--to=syzbot+69904c3b4a09e8fa2e1b@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