All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+fa1bbda326271b8808c9@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] possible deadlock in __jbd2_log_wait_for_space
Date: Sat, 19 Nov 2022 02:23:23 -0800	[thread overview]
Message-ID: <0000000000004d959d05edd036ed@google.com> (raw)
In-Reply-To: <20221119094445.4509-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: { P5776 } 2683 jiffies s: 2765 root: 0x0/T
rcu: blocking rcu_node structures (internal RCU debug):


Tested on:

commit:         15f3bff1 Add linux-next specific files for 20221116
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=130bea4e880000
kernel config:  https://syzkaller.appspot.com/x/.config?x=ec2a1d4f50866178
dashboard link: https://syzkaller.appspot.com/bug?extid=fa1bbda326271b8808c9
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=15922a21880000


       reply	other threads:[~2022-11-19 10:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221119094445.4509-1-hdanton@sina.com>
2022-11-19 10:23 ` syzbot [this message]
2022-08-08  7:33 [syzbot] possible deadlock in __jbd2_log_wait_for_space syzbot
2022-11-19  4:50 ` syzbot
2023-05-01 14:46 ` Theodore Ts'o

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=0000000000004d959d05edd036ed@google.com \
    --to=syzbot+fa1bbda326271b8808c9@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.