From: Frederic Weisbecker <frederic@kernel.org>
To: Pengfei Xu <pengfei.xu@intel.com>, Jens Axboe <axboe@kernel.dk>
Cc: lihuafei1@huawei.com, rostedt@goodmis.org,
linux-kernel@vger.kernel.org, lkp@intel.com,
quic_neeraju@quicinc.com, paulmck@kernel.org, heng.su@intel.com
Subject: Re: [Syzkaller & bisect] There is "task hung in synchronize_rcu bisect" in v6.3-rc2 kernel
Date: Thu, 13 Apr 2023 13:19:08 +0200 [thread overview]
Message-ID: <ZDflLOCujdBNXl3D@lothringen> (raw)
In-Reply-To: <ZDdsz+5/QehZ25hg@xpf.sh.intel.com>
On Thu, Apr 13, 2023 at 10:45:35AM +0800, Pengfei Xu wrote:
> Hi Huafei and kernel experts,
>
> It's a soft remind.
> This issue could be reproduced in v6.3-rc6 kernel.
> It could be reproduced on Alder lake, Raptor lake and so on x86 platforms.
> After reverted the commit "0e792b89e6800c:ftrace: Fix use-after-free for
> dynamic ftrace_ops" on top of v6.3-rc6 kernel, this issue was gone.
>
> New syzkaller reproduced code, repro.report, bisect_info.log and detailed logs
> are in link:
> https://github.com/xupengfe/syzkaller_logs/tree/main/230412_031722_synchronize_rcu
I just tested against v6.3-rc6 and again all I get is this io_ring related
issue:
[ 448.290752] INFO: task kworker/u4:0:9 blocked for more than 294 seconds.
[ 448.293868] Not tainted 6.3.0-rc6-kvm #1
[ 448.296019] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 448.299592] task:kworker/u4:0 state:D stack:0 pid:9 ppid:2 flags:0x00004000
[ 448.303397] Workqueue: events_unbound io_ring_exit_work
[ 448.305884] Call Trace:
[ 448.307147] <TASK>
[ 448.308166] __schedule+0x422/0xc90
[ 448.309824] ? wait_for_completion+0x77/0x170
[ 448.311870] schedule+0x63/0xd0
[ 448.313346] schedule_timeout+0x2fe/0x4c0
[ 448.315255] ? __this_cpu_preempt_check+0x1c/0x30
[ 448.317360] ? _raw_spin_unlock_irq+0x27/0x60
[ 448.319400] ? lockdep_hardirqs_on+0x88/0x120
[ 448.321395] ? wait_for_completion+0x77/0x170
[ 448.323462] wait_for_completion+0x9e/0x170
[ 448.325356] io_ring_exit_work+0x2b0/0x810
[ 448.327300] ? __pfx_io_tctx_exit_cb+0x10/0x10
[ 448.329345] ? _raw_spin_unlock_irq+0x27/0x60
[ 448.331397] process_one_work+0x34e/0x720
[ 448.333212] ? __pfx_io_ring_exit_work+0x10/0x10
[ 448.335377] ? process_one_work+0x34e/0x720
[ 448.337295] worker_thread+0x4e/0x530
[ 448.339079] ? __pfx_worker_thread+0x10/0x10
[ 448.341008] kthread+0x128/0x160
[ 448.342513] ? __pfx_kthread+0x10/0x10
[ 448.344305] ret_from_fork+0x2c/0x50
[ 448.346016] </TASK>
[ 448.347176]
[ 448.347176] Showing all locks held in the system:
[ 448.349887] 2 locks held by kworker/u4:0/9:
[ 448.351829] #0: ffff88807eb6dd38 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x2b4/0x720
[ 448.356362] #1: ffffc9000005fe68 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_one_work+0x2b4/0x720
[ 448.361052] 1 lock held by rcu_tasks_kthre/11:
[ 448.363142] #0: ffffffff83963450 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0x440
[ 448.367396] 1 lock held by rcu_tasks_rude_/12:
[ 448.369387] #0: ffffffff839631d0 (rcu_tasks_rude.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0x440
[ 448.373808] 1 lock held by rcu_tasks_trace/13:
[ 448.375852] #0: ffffffff83962f10 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0x440
[ 448.380434] 1 lock held by khungtaskd/30:
[ 448.382219] #0: ffffffff83963e60 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x17/0x1d0
[ 448.386291]
[ 448.387159] =============================================
[ 448.387159]
next prev parent reply other threads:[~2023-04-13 11:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 12:20 [Syzkaller & bisect] There is "task hung in synchronize_rcu bisect" in v6.3-rc2 kernel Pengfei Xu
2023-04-13 2:45 ` Pengfei Xu
2023-04-13 11:19 ` Frederic Weisbecker [this message]
2023-04-13 11:51 ` Zhang, Qiang1
2023-04-13 12:09 ` Pengfei Xu
2023-04-13 12:40 ` Jens Axboe
2023-04-13 13:55 ` Frederic Weisbecker
[not found] ` <20230413070042.1479-1-hdanton@sina.com>
2023-04-13 8:03 ` Pengfei Xu
[not found] ` <20230413083017.1518-1-hdanton@sina.com>
2023-04-13 9:08 ` Pengfei Xu
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=ZDflLOCujdBNXl3D@lothringen \
--to=frederic@kernel.org \
--cc=axboe@kernel.dk \
--cc=heng.su@intel.com \
--cc=lihuafei1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=paulmck@kernel.org \
--cc=pengfei.xu@intel.com \
--cc=quic_neeraju@quicinc.com \
--cc=rostedt@goodmis.org \
/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.