From: syzbot <syzbot+6fb78d577e89e69602f9@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in call_timer_fn
Date: Wed, 16 Nov 2022 17:35:18 -0800 [thread overview]
Message-ID: <0000000000000b539d05eda09a88@google.com> (raw)
In-Reply-To: <20221117010835.3474-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: { P4107 } 2643 jiffies s: 2809 root: 0x0/T
rcu: blocking rcu_node structures (internal RCU debug):
Tested on:
commit: 7eba4505 net: dcb: move getapptrust to separate function
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=12b65845880000
kernel config: https://syzkaller.appspot.com/x/.config?x=893a728fb1a6b263
dashboard link: https://syzkaller.appspot.com/bug?extid=6fb78d577e89e69602f9
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=14ef644e880000
next parent reply other threads:[~2022-11-17 1:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221117010835.3474-1-hdanton@sina.com>
2022-11-17 1:35 ` syzbot [this message]
2022-11-16 15:25 [syzbot] WARNING in call_timer_fn syzbot
2022-11-16 18:29 ` Thomas Gleixner
[not found] ` <20221117024511.3606-1-hdanton@sina.com>
2022-11-17 11:54 ` Thomas Gleixner
[not found] ` <20221117125523.3783-1-hdanton@sina.com>
2022-11-17 16:06 ` Thomas Gleixner
2022-11-17 21:04 ` Luiz Augusto von Dentz
2022-11-17 21:16 ` Luiz Augusto von Dentz
2022-11-18 0:53 ` Tetsuo Handa
2022-11-18 1:17 ` Thomas Gleixner
[not found] ` <20221118012805.3862-1-hdanton@sina.com>
2022-11-18 20:01 ` Luiz Augusto von Dentz
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=0000000000000b539d05eda09a88@google.com \
--to=syzbot+6fb78d577e89e69602f9@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