From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 214767] xfs seems to hang due to race condition? maybe related to (gratuitous) thaw.
Date: Wed, 20 Oct 2021 16:16:12 +0000 [thread overview]
Message-ID: <bug-214767-201763-wFcOwnSq0o@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214767-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214767
--- Comment #2 from Christian Theune (ct@flyingcircus.io) ---
Here's another excerpt that I dug out from a different VM with the same issue.
No thawing happening AFAICT around this time:
[848865.353541] INFO: task nix-daemon:1855245 blocked for more than 122
seconds.
[848865.355625] Not tainted 5.10.70 #1-NixOS
[848865.356912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[848865.359117] task:nix-daemon state:D stack: 0 pid:1855245 ppid:
2165 flags:0x00000000
[848865.360999] Call Trace:
[848865.361480] __schedule+0x271/0x860
[848865.362069] schedule+0x46/0xb0
[848865.362657] xfs_log_commit_cil+0x6a4/0x800 [xfs]
[848865.363436] ? wake_up_q+0xa0/0xa0
[848865.364026] __xfs_trans_commit+0x9d/0x310 [xfs]
[848865.364818] xfs_create+0x472/0x560 [xfs]
[848865.365517] xfs_generic_create+0x247/0x320 [xfs]
[848865.366310] ? xfs_lookup+0x55/0x100 [xfs]
[848865.366984] path_openat+0xdd7/0x1070
[848865.367617] do_filp_open+0x88/0x130
[848865.368199] ? getname_flags.part.0+0x29/0x1a0
[848865.368925] do_sys_openat2+0x97/0x150
[848865.369557] __x64_sys_openat+0x54/0x90
[848865.370176] do_syscall_64+0x33/0x40
[848865.370787] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[848865.371619] RIP: 0033:0x7f48b24c0ea8
[848865.372196] RSP: 002b:00007ffed91cee30 EFLAGS: 00000293 ORIG_RAX:
0000000000000101
[848865.373398] RAX: ffffffffffffffda RBX: 00000000000800c1 RCX:
00007f48b24c0ea8
[848865.374530] RDX: 00000000000800c1 RSI: 00000000015c4750 RDI:
00000000ffffff9c
[848865.375661] RBP: 00000000015c4750 R08: 0000000000000000 R09:
0000000000000003
[848865.376790] R10: 00000000000001b6 R11: 0000000000000293 R12:
00007ffed91cf220
[848865.377920] R13: 00007ffed91ceee0 R14: 00007ffed91ceed0 R15:
00007ffed91d0c50
and I can see it not making any progress:
[848988.235884] INFO: task nix-daemon:1855245 blocked for more than 245
seconds.
[848988.238567] Not tainted 5.10.70 #1-NixOS
[848988.240254] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[848988.242358] task:nix-daemon state:D stack: 0 pid:1855245 ppid:
2165 flags:0x00000000
[848988.243756] Call Trace:
[848988.244183] __schedule+0x271/0x860
[848988.244780] schedule+0x46/0xb0
[848988.245366] xfs_log_commit_cil+0x6a4/0x800 [xfs]
[848988.246153] ? wake_up_q+0xa0/0xa0
[848988.246775] __xfs_trans_commit+0x9d/0x310 [xfs]
[848988.247572] xfs_create+0x472/0x560 [xfs]
[848988.248269] xfs_generic_create+0x247/0x320 [xfs]
[848988.249084] ? xfs_lookup+0x55/0x100 [xfs]
[848988.249781] path_openat+0xdd7/0x1070
[848988.250388] do_filp_open+0x88/0x130
[848988.251000] ? getname_flags.part.0+0x29/0x1a0
[848988.251746] do_sys_openat2+0x97/0x150
[848988.252366] __x64_sys_openat+0x54/0x90
[848988.253015] do_syscall_64+0x33/0x40
[848988.253610] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[848988.254445] RIP: 0033:0x7f48b24c0ea8
[848988.255071] RSP: 002b:00007ffed91cee30 EFLAGS: 00000293 ORIG_RAX:
0000000000000101
[848988.256292] RAX: ffffffffffffffda RBX: 00000000000800c1 RCX:
00007f48b24c0ea8
[848988.257460] RDX: 00000000000800c1 RSI: 00000000015c4750 RDI:
00000000ffffff9c
[848988.258622] RBP: 00000000015c4750 R08: 0000000000000000 R09:
0000000000000003
[848988.259777] R10: 00000000000001b6 R11: 0000000000000293 R12:
00007ffed91cf220
[848988.260933] R13: 00007ffed91ceee0 R14: 00007ffed91ceed0 R15:
00007ffed91d0c50
Both stack traces are identical in every regard so that might be useful info.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-10-20 16:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 7:36 [Bug 214767] New: xfs seems to hang due to race condition? maybe related to (gratuitous) thaw bugzilla-daemon
2021-10-20 7:39 ` [Bug 214767] " bugzilla-daemon
2021-10-20 16:16 ` bugzilla-daemon [this message]
2021-10-20 16:31 ` bugzilla-daemon
2021-10-20 18:29 ` bugzilla-daemon
2021-10-20 18:37 ` bugzilla-daemon
2021-10-20 19:22 ` bugzilla-daemon
2021-10-20 19:26 ` bugzilla-daemon
2021-10-20 22:16 ` [Bug 214767] New: " Dave Chinner
2021-10-20 22:38 ` [Bug 214767] " bugzilla-daemon
2021-10-21 4:21 ` bugzilla-daemon
2021-10-21 13:17 ` bugzilla-daemon
2021-10-21 13:19 ` bugzilla-daemon
2021-10-21 13:20 ` bugzilla-daemon
2021-10-29 2:21 ` bugzilla-daemon
2021-10-29 2:22 ` bugzilla-daemon
2021-11-09 5:19 ` bugzilla-daemon
2021-11-10 15:16 ` bugzilla-daemon
2021-11-20 22:31 ` Dave Chinner
2021-11-20 22:31 ` bugzilla-daemon
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=bug-214767-201763-wFcOwnSq0o@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).