All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+3fd8326d9a0812d19218@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING: refcount bug in nldev_newlink
Date: Sun, 11 Dec 2022 02:42:16 -0800	[thread overview]
Message-ID: <0000000000005d216f05ef8b0a6e@google.com> (raw)
In-Reply-To: <20221211014342.2302-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: { P5545 } 2629 jiffies s: 2809 root: 0x0/T
rcu: blocking rcu_node structures (internal RCU debug):


Tested on:

commit:         591cd615 Add linux-next specific files for 20221207
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=13b5948f880000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8b2d3e63e054c24f
dashboard link: https://syzkaller.appspot.com/bug?extid=3fd8326d9a0812d19218
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=1119320b880000


       reply	other threads:[~2022-12-11 10:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221211014342.2302-1-hdanton@sina.com>
2022-12-11 10:42 ` syzbot [this message]
2022-12-07 20:51 [syzbot] WARNING: refcount bug in nldev_newlink syzbot
2022-12-08  9:14 ` Leon Romanovsky
2022-12-08 11:42   ` Guoqing Jiang
2022-12-08 11:54     ` Leon Romanovsky
2022-12-09  0:48       ` Guoqing Jiang
2022-12-09 13:01   ` Jason Gunthorpe
     [not found]   ` <20221209134229.1987-1-hdanton@sina.com>
2022-12-09 14:06     ` Jason Gunthorpe

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=0000000000005d216f05ef8b0a6e@google.com \
    --to=syzbot+3fd8326d9a0812d19218@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.