From: RlndVt <RlndVt@protonmail.com>
To: "linux-bcachefs@vger.kernel.org" <linux-bcachefs@vger.kernel.org>
Subject: [bcachefs] Stack-trace at fs/bcachefs/btree_iter.c:2825 bch2_trans_srcu_unlock+0x116/0x120
Date: Sun, 19 May 2024 12:26:31 +0000 [thread overview]
Message-ID: <gUWINkhdQo_PMB51THavPfA3ro8y3Xpj62Xpm2bBreMiP9U7R44oxZVKj1h4MGfdGatzKw_J6AMA7tnd5f6I5hp4cXbIFCypdlZtK8Xb_gA=@protonmail.com> (raw)
Hi Kent,
My system is reporting the following stack-trace. I am not noticing anything odd. I believe it happened at unmount; however the following mount reports a clean unmount. fsck doesn't report any problem.
Let me know if I can provide more info.
Regards,
Roland
May 19 10:34:38 cleop.domain.name kernel: ------------[ cut here ]------------May 19 10:34:38 cleop.domain.name kernel: btree trans held srcu lock (delaying memory reclaim) for 25 seconds
May 19 10:34:38 cleop.domain.name kernel: WARNING: CPU: 5 PID: 7396 at fs/bcachefs/btree_iter.c:2825 bch2_trans_srcu_unlock+0x116/0x120 [bcachefs]
May 19 10:34:38 cleop.domain.name kernel: Modules linked in: bcachefs lz4hc_compress lz4_compress rpcrdma rdma_cm iw_cm ib_cm ib_core nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib>
May 19 10:34:38 cleop.domain.name kernel: kvm_intel snd_hwdep iTCO_wdt intel_pmc_bxt iTCO_vendor_support snd_pcm mei_hdcp ee1004 mei_pxp snd_timer kvm eeepc_wmi asus_wmi irqbypass rapl le>
May 19 10:34:38 cleop.domain.name kernel: CPU: 5 PID: 7396 Comm: bch-rebalance/b Not tainted 6.8.9-300.fc40.x86_64 #1
May 19 10:34:38 cleop.domain.name kernel: Hardware name: ASUS System Product Name/PRIME B460I-PLUS, BIOS 1301 07/13/2021
May 19 10:34:38 cleop.domain.name kernel: RIP: 0010:bch2_trans_srcu_unlock+0x116/0x120 [bcachefs]
May 19 10:34:38 cleop.domain.name kernel: Code: dc 86 d5 48 c7 c7 f8 a0 d0 c1 48 b9 cf f7 53 e3 a5 9b c4 20 48 29 d0 48 c1 e8 03 48 f7 e1 48 89 d6 48 c1 ee 04 e8 9a e9 58 d3 <0f> 0b eb 8b >
May 19 10:34:38 cleop.domain.name kernel: RSP: 0018:ffffad5c40947d70 EFLAGS: 00010282
May 19 10:34:38 cleop.domain.name kernel: RAX: 0000000000000000 RBX: ffff9853e5694000 RCX: 0000000000000027
May 19 10:34:38 cleop.domain.name kernel: RDX: ffff9862aeca18c8 RSI: 0000000000000001 RDI: ffff9862aeca18c0
May 19 10:34:38 cleop.domain.name kernel: RBP: ffff9853d2d00000 R08: 0000000000000000 R09: 73646e6f63657320
May 19 10:34:38 cleop.domain.name kernel: R10: ffffffffc1d0a13c R11: 0000000000000000 R12: ffff9853d2d00000
May 19 10:34:38 cleop.domain.name kernel: R13: ffffad5c40947e98 R14: ffff9853d2d00000 R15: ffffffffc1c37950
May 19 10:34:38 cleop.domain.name kernel: FS: 0000000000000000(0000) GS:ffff9862aec80000(0000) knlGS:0000000000000000
May 19 10:34:38 cleop.domain.name kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 19 10:34:38 cleop.domain.name kernel: CR2: 000055f5330599e0 CR3: 0000000d12428002 CR4: 00000000003706f0
May 19 10:34:38 cleop.domain.name kernel: Call Trace:
May 19 10:34:38 cleop.domain.name kernel: <TASK>
May 19 10:34:38 cleop.domain.name kernel: ? bch2_trans_srcu_unlock+0x116/0x120 [bcachefs]
May 19 10:34:38 cleop.domain.name kernel: ? __warn+0x81/0x130
May 19 10:34:38 cleop.domain.name kernel: ? bch2_trans_srcu_unlock+0x116/0x120 [bcachefs]
May 19 10:34:38 cleop.domain.name kernel: ? report_bug+0x16f/0x1a0
May 19 10:34:38 cleop.domain.name kernel: ? handle_bug+0x3c/0x80
May 19 10:34:38 cleop.domain.name kernel: ? exc_invalid_op+0x17/0x70
May 19 10:34:38 cleop.domain.name kernel: ? asm_exc_invalid_op+0x1a/0x20
May 19 10:34:38 cleop.domain.name kernel: ? __pfx_bch2_rebalance_thread+0x10/0x10 [bcachefs]
May 19 10:34:38 cleop.domain.name kernel: ? bch2_trans_srcu_unlock+0x116/0x120 [bcachefs]
May 19 10:34:38 cleop.domain.name kernel: bch2_moving_ctxt_flush_all+0x5c/0x140 [bcachefs]
May 19 10:34:38 cleop.domain.name kernel: ? mutex_lock+0x12/0x30
May 19 10:34:38 cleop.domain.name kernel: bch2_moving_ctxt_exit+0x1f/0xb0 [bcachefs]
May 19 10:34:38 cleop.domain.name kernel: bch2_rebalance_thread+0x7b/0xb0 [bcachefs]
May 19 10:34:38 cleop.domain.name kernel: ? bch2_rebalance_thread+0x5c/0xb0 [bcachefs]
May 19 10:34:38 cleop.domain.name kernel: kthread+0xe5/0x120
May 19 10:34:38 cleop.domain.name kernel: ? __pfx_kthread+0x10/0x10
May 19 10:34:38 cleop.domain.name kernel: ret_from_fork+0x31/0x50
May 19 10:34:38 cleop.domain.name kernel: ? __pfx_kthread+0x10/0x10
May 19 10:34:38 cleop.domain.name kernel: ret_from_fork_asm+0x1b/0x30
May 19 10:34:38 cleop.domain.name kernel: </TASK>
May 19 10:34:38 cleop.domain.name kernel: ---[ end trace 0000000000000000 ]---
reply other threads:[~2024-05-19 12:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='gUWINkhdQo_PMB51THavPfA3ro8y3Xpj62Xpm2bBreMiP9U7R44oxZVKj1h4MGfdGatzKw_J6AMA7tnd5f6I5hp4cXbIFCypdlZtK8Xb_gA=@protonmail.com' \
--to=rlndvt@protonmail.com \
--cc=linux-bcachefs@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 read-only IMAP folder(s) and NNTP newsgroup(s).