Messages in this thread |  | | Date | Sun, 20 Mar 2022 18:32:12 -0700 | Subject | Re: [syzbot] INFO: rcu detected stall in gc_worker (3) | From | syzbot <> |
| |
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue: INFO: rcu detected stall in corrupted
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_batadv: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 0-... } 2628 jiffies s: 2065 root: 0x1/. rcu: blocking rcu_node structures (internal RCU debug): Task dump for CPU 0: task:syz-executor354 state:R running task stack:27224 pid: 4078 ppid: 4061 flags:0x0000400e Call Trace: <TASK> </TASK>
Tested on:
commit: 91265a6d Add linux-next specific files for 20220303 git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/ console output: https://syzkaller.appspot.com/x/log.txt?x=16355271700000 kernel config: https://syzkaller.appspot.com/x/.config?x=617f79440a35673a dashboard link: https://syzkaller.appspot.com/bug?extid=eec403943a2a2455adaa 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=17b1f271700000
|  |