From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 219504] XFS crashes with kernel Version > 6.1.91. Perhaps Changes in kernel 6.1.92 for XFS/iomap causing the problems?
Date: Thu, 19 Dec 2024 13:58:38 +0000 [thread overview]
Message-ID: <bug-219504-201763-muHGWZfemd@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219504-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219504
Mike-SPC (speedcracker@hotmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|XFS |Other
Kernel Version|6.1.92 and up |since 6.1.92 and up
Product|File System |IO/Storage
--- Comment #3 from Mike-SPC (speedcracker@hotmail.com) ---
Hi there,
rechecked the newest kernel version 6.1.120.
Get the same problem.
Here is the kernel-backtrace:
[Thu Dec 19 14:03:21 2024] ------------[ cut here ]------------
[Thu Dec 19 14:03:21 2024] WARNING: CPU: 0 PID: 24318 at
fs/iomap/buffered-io.c:980 iomap_file_buffered_write_punch_delalloc+0x398/0x440
[Thu Dec 19 14:03:21 2024] Modules linked in: iscsi_scst(O) scst_vdisk(O)
scst(O) dlm quota_v2 quota_tree autofs4 tcp_bbr sch_fq udf crc_itu_t ses
enclosure hid_generic wmi_bmof usbhid edac_mce_amd uas crc32_pclmul aesni_intel
hid crypto_simd usb_storage rapl bnx2 i2c_piix4 r8169 pcspkr k10temp ccp
i2c_core sha1_generic video mpt3sas backlight wmi
[Thu Dec 19 14:03:21 2024] CPU: 0 PID: 24318 Comm: disk014_0 Tainted: G S
O 6.1.120_LFS_FILE01 #1
[Thu Dec 19 14:03:21 2024] Hardware name: To Be Filled By O.E.M. X370 Pro4/X370
Pro4, BIOS P10.08 01/22/2024
[Thu Dec 19 14:03:21 2024] EIP:
iomap_file_buffered_write_punch_delalloc+0x398/0x440
[Thu Dec 19 14:03:21 2024] Code: 84 8d 00 00 00 8b 45 e0 8b 40 20 83 c0 10 e8
2f 31 e0 ff 83 c4 44 89 f0 5b 5e 5f 5d e9 f5 31 8e 00 90 0f 0b e9 13 fe ff ff
90 <0f> 0b e9 fd fd ff ff 90 0f 0b e9 6b fe ff ff 90 0f 0b 8d b6 00 00
[Thu Dec 19 14:03:21 2024] EAX: bb68e000 EBX: ffffff85 ECX: bb68f000 EDX:
0000007b
[Thu Dec 19 14:03:21 2024] ESI: bb68f000 EDI: 00000000 EBP: 5137fbd0 ESP:
5137fb80
[Thu Dec 19 14:03:21 2024] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS:
00010293
[Thu Dec 19 14:03:21 2024] CR0: 80050033 CR2: 0175a2d0 CR3: 03d1b720 CR4:
00350ef0
[Thu Dec 19 14:03:21 2024] Call Trace:
[Thu Dec 19 14:03:21 2024] ? show_regs.cold+0x16/0x1b
[Thu Dec 19 14:03:21 2024] ?
iomap_file_buffered_write_punch_delalloc+0x398/0x440
[Thu Dec 19 14:03:21 2024] ? __warn+0x87/0xe0
[Thu Dec 19 14:03:21 2024] ?
iomap_file_buffered_write_punch_delalloc+0x398/0x440
[Thu Dec 19 14:03:21 2024] ?
iomap_file_buffered_write_punch_delalloc+0x398/0x440
[Thu Dec 19 14:03:21 2024] ? report_bug+0xe5/0x170
[Thu Dec 19 14:03:21 2024] ? exc_overflow+0x60/0x60
[Thu Dec 19 14:03:21 2024] ? handle_bug+0x2a/0x50
[Thu Dec 19 14:03:21 2024] ? exc_invalid_op+0x1e/0x70
[Thu Dec 19 14:03:21 2024] ? handle_exception+0x101/0x101
[Thu Dec 19 14:03:21 2024] ? exc_overflow+0x60/0x60
[Thu Dec 19 14:03:21 2024] ?
iomap_file_buffered_write_punch_delalloc+0x398/0x440
[Thu Dec 19 14:03:21 2024] ? exc_overflow+0x60/0x60
[Thu Dec 19 14:03:21 2024] ?
iomap_file_buffered_write_punch_delalloc+0x398/0x440
[Thu Dec 19 14:03:21 2024] ? xfs_dax_write_iomap_end+0xa0/0xa0
[Thu Dec 19 14:03:21 2024] ? xfs_buffered_write_iomap_end+0x52/0xc0
[Thu Dec 19 14:03:21 2024] ? xfs_buffered_write_iomap_end+0xc0/0xc0
[Thu Dec 19 14:03:21 2024] ? iomap_iter+0xce/0x4b0
[Thu Dec 19 14:03:21 2024] ? xfs_dax_write_iomap_end+0xa0/0xa0
[Thu Dec 19 14:03:21 2024] ? iomap_file_buffered_write+0xa9/0x420
[Thu Dec 19 14:03:21 2024] ? xfs_file_buffered_write+0x9d/0x2e0
[Thu Dec 19 14:03:21 2024] ? xfs_file_write_iter+0xc9/0x100
[Thu Dec 19 14:03:21 2024] ? fileio_exec_async+0x25e/0x3a0 [scst_vdisk]
[Thu Dec 19 14:03:21 2024] ? fileio_exec_write+0x2ce/0x400 [scst_vdisk]
[Thu Dec 19 14:03:21 2024] ? vdev_do_job+0x36/0xe0 [scst_vdisk]
[Thu Dec 19 14:03:21 2024] ? fileio_exec+0x1f/0x30 [scst_vdisk]
[Thu Dec 19 14:03:21 2024] ? scst_do_real_exec+0x51/0x130 [scst]
[Thu Dec 19 14:03:21 2024] ? scst_exec_check_blocking+0xa8/0x220 [scst]
[Thu Dec 19 14:03:21 2024] ? scst_process_active_cmd+0x200/0x18f0 [scst]
[Thu Dec 19 14:03:21 2024] ? scst_cmd_thread+0x15c/0x500 [scst]
[Thu Dec 19 14:03:21 2024] ? prepare_to_wait_event+0x160/0x160
[Thu Dec 19 14:03:21 2024] ? kthread+0xd2/0x100
[Thu Dec 19 14:03:21 2024] ? scst_cmd_done_local+0x90/0x90 [scst]
[Thu Dec 19 14:03:21 2024] ? kthread_complete_and_exit+0x20/0x20
[Thu Dec 19 14:03:21 2024] ? ret_from_fork+0x1c/0x28
[Thu Dec 19 14:03:21 2024] ---[ end trace 0000000000000000 ]---
Thanks in advance and for investigation,
Mike
--
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:[~2024-12-19 13:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 13:42 [Bug 219504] New: XFS crashes with kernel Version > 6.1.91. Perhaps Changes in kernel 6.1.92 for XFS/iomap causing the problems? bugzilla-daemon
2024-11-21 11:49 ` [Bug 219504] " bugzilla-daemon
2024-11-28 21:09 ` bugzilla-daemon
2024-12-19 13:58 ` bugzilla-daemon [this message]
2024-12-19 17:02 ` [Bug 219504] XFS crashes with kernel Version > 6.1.91. Perhaps Changes in kernel 6.1.92 (and up) " bugzilla-daemon
2024-12-30 21:26 ` [Bug 219504] New: XFS crashes with kernel Version > 6.1.91. Perhaps Changes in kernel 6.1.92 " Marco Nelissen
2024-12-30 21:26 ` [Bug 219504] iomap/buffered-io/XFS crashes with kernel Version > 6.1.91. Perhaps Changes in kernel 6.1.92 (and up) " bugzilla-daemon
2024-12-31 22:11 ` [Bug 219504] New: XFS crashes with kernel Version > 6.1.91. Perhaps Changes in kernel 6.1.92 " Marco Nelissen
2024-12-31 22:11 ` [Bug 219504] iomap/buffered-io/XFS crashes with kernel Version > 6.1.91. Perhaps Changes in kernel 6.1.92 (and up) " bugzilla-daemon
2025-01-18 14:00 ` bugzilla-daemon
2025-01-18 23:51 ` Marco Nelissen
2025-01-18 23:51 ` bugzilla-daemon
2025-01-28 20:00 ` bugzilla-daemon
2025-02-03 10:03 ` 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-219504-201763-muHGWZfemd@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 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.