public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+a8cdfe2d8ad35db3a7fd@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernfs?] INFO: task hung in do_coredump (3)
Date: Wed, 30 Oct 2024 04:21:02 -0700	[thread overview]
Message-ID: <6722169e.050a0220.35b515.001a.GAE@google.com> (raw)
In-Reply-To: <20241030105839.2547-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: { P1029 } 3639 jiffies s: 9185 root: 0x0/T
rcu: blocking rcu_node structures (internal RCU debug):


Tested on:

commit:         c1e939a2 Merge tag 'cgroup-for-6.12-rc5-fixes' of git:..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1408e540580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1940f73a609bb874
dashboard link: https://syzkaller.appspot.com/bug?extid=a8cdfe2d8ad35db3a7fd
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1620e540580000


  reply	other threads:[~2024-10-30 11:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  9:02 [syzbot] [kernfs?] INFO: task hung in do_coredump (3) syzbot
2024-10-20  9:30 ` syzbot
2024-10-28 22:23 ` syzbot
2024-10-29 11:07   ` Hillf Danton
2024-10-29 11:29     ` syzbot
2024-10-30 10:58   ` Hillf Danton
2024-10-30 11:21     ` syzbot [this message]
2024-11-01 11:16   ` Hillf Danton
2024-11-01 11:41     ` syzbot
2025-07-07 16:27 ` [syzbot] [fs?] " syzbot
2025-07-08  8:24   ` Pavel Begunkov

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=6722169e.050a0220.35b515.001a.GAE@google.com \
    --to=syzbot+a8cdfe2d8ad35db3a7fd@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