From: Bruno Goncalves <bgoncalv@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: fstests@vger.kernel.org, CKI Project <cki-project@redhat.com>
Subject: 1 lock held by xfs_repair/276634
Date: Thu, 1 Jul 2021 12:44:30 +0200 [thread overview]
Message-ID: <CA+QYu4pPRr-KQB2b1YsZSYfAb11_hnL+UH8WTj3N5_x9yX8WnA@mail.gmail.com> (raw)
Hello,
We have hit this lock problem during xfstest [1] on aarch64. The whole
console.log is available on [2].
10847.013727] run fstests generic/023 at 2021-05-15 17:21:46
[10863.635560] XFS (sda4): Unmounting Filesystem
[10865.095328] BUG: sleeping function called from invalid context at (null):3550
[10865.102695] in_atomic(): 0, irqs_disabled(): 128, non_block: 0,
pid: 276634, name: xfs_repair
[10865.111223] 1 lock held by xfs_repair/276634:
[10865.115579] #0: ffff000168f654d0
(&tsk->futex_exit_mutex){+.+.}-{3:3}, at: futex_exit_release+0x40/0xe4
[10865.125091] irq event stamp: 150
[10865.128314] hardirqs last enabled at (149): [<ffff8000101a2778>]
uaccess_ttbr0_enable+0xa8/0xc0
[10865.137096] hardirqs last disabled at (150): [<ffff8000101a2838>]
uaccess_ttbr0_disable+0xa8/0xb4
[10865.145964] softirqs last enabled at (132): [<ffff800010016490>]
put_cpu_fpsimd_context+0x30/0x70
[10865.154921] softirqs last disabled at (130): [<ffff800010016408>]
get_cpu_fpsimd_context+0x8/0x60
[10865.163792] CPU: 31 PID: 276634 Comm: xfs_repair Not tainted 5.13.0-rc1 #1
[10865.170663] Hardware name: GIGABYTE R120-T34-00/MT30-GS2-00, BIOS
F02 08/06/2019
[10865.178054] Call trace:
[10865.180496] dump_backtrace+0x0/0x1c0
[10865.184156] show_stack+0x24/0x30
[10865.187467] dump_stack+0xf8/0x164
[10865.190867] ___might_sleep+0x174/0x250
[10865.194700] __might_sleep+0x60/0xa0
[10865.198272] __might_fault+0x3c/0x90
[10865.201847] exit_robust_list+0xac/0x36c
[10865.205767] exit_robust_list+0x9c/0x36c
[10865.209686] futex_exit_release+0xa8/0xe4
[10865.213692] exit_mm_release+0x28/0x44
[10865.217438] exit_mm+0x2c/0x27c
[10865.220579] do_exit+0x1f0/0x454
[10865.223804] __arm64_sys_exit+0x24/0x2c
[10865.227638] invoke_syscall+0x50/0x120
[10865.231384] el0_svc_common.constprop.0+0x68/0x104
[10865.236172] do_el0_svc+0x30/0x9c
[10865.239483] el0_svc+0x2c/0x54
[10865.242538] el0_sync_handler+0x1a4/0x1b0
[10865.246544] el0_sync+0x19c/0x1c0
We don't reproduce this often, but the first time I've seen it was
with 'Commit: f36edc5533b2 - Merge tag 'arc-5.13-rc2' of
git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc'
[1] https://gitlab.com/cki-project/kernel-tests/-/tree/main/filesystems/xfs/xfstests
[2] https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/05/15/303402899/build_aarch64_redhat%3A1264727321/tests/9991652_aarch64_2_console.log
Thank you,
Bruno Goncalves
next reply other threads:[~2021-07-01 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 10:44 Bruno Goncalves [this message]
2021-07-02 0:05 ` 1 lock held by xfs_repair/276634 Dave Chinner
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=CA+QYu4pPRr-KQB2b1YsZSYfAb11_hnL+UH8WTj3N5_x9yX8WnA@mail.gmail.com \
--to=bgoncalv@redhat.com \
--cc=cki-project@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-fsdevel@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).