All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+eec403943a2a2455adaa@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: rcu detected stall in gc_worker (3)
Date: Sun, 31 Jul 2022 01:31:08 -0700	[thread overview]
Message-ID: <0000000000007e808205e515b47d@google.com> (raw)
In-Reply-To: <20220731081548.659-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: { 0-... } 2654 jiffies s: 2049 root: 0x1/.
rcu: blocking rcu_node structures (internal RCU debug):
Task dump for CPU 0:
task:syz-executor.0  state:R  running task     stack:27224 pid: 4073 ppid:  4053 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=11978a82080000
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=14ff72fe080000


       reply	other threads:[~2022-07-31  8:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220731081548.659-1-hdanton@sina.com>
2022-07-31  8:31 ` syzbot [this message]
     [not found] <20220731094805.847-1-hdanton@sina.com>
2022-07-31 10:09 ` [syzbot] INFO: rcu detected stall in gc_worker (3) syzbot
     [not found] <20220731074633.519-1-hdanton@sina.com>
2022-07-31  8:03 ` syzbot
     [not found] <20220321063053.2877-1-hdanton@sina.com>
2022-03-21  6:43 ` syzbot
     [not found]   ` <20220321080843.3060-1-hdanton@sina.com>
2022-03-21 21:01     ` Paul E. McKenney
     [not found] <20220321031535.2804-1-hdanton@sina.com>
2022-03-21  3:23 ` syzbot
     [not found] <20220321012046.2729-1-hdanton@sina.com>
2022-03-21  1:32 ` syzbot
     [not found] <20220320152154.2662-1-hdanton@sina.com>
2022-03-20 15:33 ` syzbot
2022-03-20 12:02 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=0000000000007e808205e515b47d@google.com \
    --to=syzbot+eec403943a2a2455adaa@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.