* Re: Bug using new ntfs3 file system driver (5.15.2 on Arch Linux)
@ 2021-11-27 14:13 Mohan R
2021-11-27 14:50 ` Matthew Wilcox
0 siblings, 1 reply; 8+ messages in thread
From: Mohan R @ 2021-11-27 14:13 UTC (permalink / raw)
To: uwe.sauter.de; +Cc: almaz.alexandrovich, linux-fsdevel, ntfs3, willy
Hi,
I confirm this issue. I tried to rsync between two ntfs3 mounts, but
rsync got killed unexpectedly.
Nov 27 19:21:53 mohanlaptop0 kernel: BUG: unable to handle page fault
for address: ffffb9c24fb74000
Nov 27 19:21:53 mohanlaptop0 kernel: #PF: supervisor read access in kernel mode
Nov 27 19:21:53 mohanlaptop0 kernel: #PF: error_code(0x0000) - not-present page
Nov 27 19:21:53 mohanlaptop0 kernel: PGD 100000067 P4D 100000067 PUD
1001bd067 PMD 10460a067 PTE 0
Nov 27 19:21:53 mohanlaptop0 kernel: Oops: 0000 [#2] PREEMPT SMP NOPTI
Nov 27 19:21:53 mohanlaptop0 kernel: CPU: 5 PID: 144039 Comm: rsync
Not tainted 5.15.5-arch1-1 #1 f0168f793e3f707b46715a62fafabd6a40826924
Nov 27 19:21:53 mohanlaptop0 kernel: Hardware name: Dell Inc. Inspiron
14 5410/0CKN95, BIOS 2.2.1 07/27/2021
Nov 27 19:21:53 mohanlaptop0 kernel: RIP: 0010:show_trace_log_lvl+0x1a4/0x32d
Nov 27 19:21:53 mohanlaptop0 kernel: Code: c7 14 60 a5 86 e8 0f be 00
00 4d 85 ed 74 41 0f b6 95 37 ff ff ff 4c 89 f1 4c 89 ee 48 8d bd 50
ff ff ff e8 dc fd ff ff eb 26 <4c> 8b 3b 48 8d bd 70 ff ff ff e8 2e 4e
52 ff 4c 89 ff 48 89 85 28
Nov 27 19:21:53 mohanlaptop0 kernel: RSP: 0018:ffffb9c24fb738d8 EFLAGS: 00010012
Nov 27 19:21:53 mohanlaptop0 kernel: RAX: 0000000000000000 RBX:
ffffb9c24fb73fff RCX: 0000000000000000
Nov 27 19:21:53 mohanlaptop0 kernel: RDX: 0000000000000000 RSI:
0000000000000000 RDI: 0000000000000000
Nov 27 19:21:53 mohanlaptop0 kernel: RBP: ffffb9c24fb739b8 R08:
0000000000000000 R09: 0000000000000000
Nov 27 19:21:53 mohanlaptop0 kernel: R10: 0000000000000000 R11:
0000000000000000 R12: ffff949c432b0000
Nov 27 19:21:53 mohanlaptop0 kernel: R13: 0000000000000000 R14:
ffffffff86a7d25f R15: 0000000000002b00
Nov 27 19:21:53 mohanlaptop0 kernel: FS: 00007f40259b8580(0000)
GS:ffff949dc7740000(0000) knlGS:0000000000000000
Nov 27 19:21:53 mohanlaptop0 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Nov 27 19:21:53 mohanlaptop0 kernel: CR2: ffffb9c24fb74000 CR3:
00000001b114c005 CR4: 0000000000770ee0
Nov 27 19:21:53 mohanlaptop0 kernel: PKRU: 55555554
Nov 27 19:21:53 mohanlaptop0 kernel: Call Trace:
Nov 27 19:21:53 mohanlaptop0 kernel: <TASK>
Nov 27 19:21:53 mohanlaptop0 kernel: __die_body.cold+0x1a/0x1f
Nov 27 19:21:53 mohanlaptop0 kernel: page_fault_oops+0x19e/0x310
Nov 27 19:21:53 mohanlaptop0 kernel: exc_page_fault+0xda/0x180
Nov 27 19:21:53 mohanlaptop0 kernel: asm_exc_page_fault+0x1e/0x30
Nov 27 19:21:53 mohanlaptop0 kernel: RIP: 0010:0xffffff8586d685ff
Nov 27 19:21:53 mohanlaptop0 kernel: Code: Unable to access opcode
bytes at RIP 0xffffff8586d685d5.
Nov 27 19:21:53 mohanlaptop0 kernel: RSP: 0018:ffffb9c24fb73b4f EFLAGS: 00010246
Nov 27 19:21:53 mohanlaptop0 kernel: RAX: 0000000000000000 RBX:
0000000000001700 RCX: 0000000000000000
Nov 27 19:21:53 mohanlaptop0 kernel: RDX: 0000000000000000 RSI:
0000000000000000 RDI: 0000000000000000
Nov 27 19:21:53 mohanlaptop0 kernel: RBP: ffb9c24fb73c3800 R08:
0000000000000000 R09: 0000000000000000
Nov 27 19:21:53 mohanlaptop0 kernel: R10: 0000000000000000 R11:
0000000000000000 R12: ff949b43a8426800
Nov 27 19:21:53 mohanlaptop0 kernel: R13: 00000001112ccaff R14:
fff6a0c99d400000 R15: 00000000000056ff
Nov 27 19:21:53 mohanlaptop0 kernel: ? page_cache_ra_unbounded+0x1c5/0x250
Nov 27 19:21:53 mohanlaptop0 kernel: ? filemap_get_pages+0x269/0x730
Nov 27 19:21:53 mohanlaptop0 kernel: ? filemap_read+0xb9/0x360
Nov 27 19:21:53 mohanlaptop0 kernel: ? new_sync_read+0x156/0x1f0
Nov 27 19:21:53 mohanlaptop0 kernel: ? vfs_read+0xff/0x1a0
Nov 27 19:21:53 mohanlaptop0 kernel: ? ksys_read+0x67/0xf0
Nov 27 19:21:53 mohanlaptop0 kernel: ? do_syscall_64+0x59/0x90
Nov 27 19:21:53 mohanlaptop0 kernel: ? do_syscall_64+0x69/0x90
Nov 27 19:21:53 mohanlaptop0 kernel: ? syscall_exit_to_user_mode+0x23/0x50
Nov 27 19:21:53 mohanlaptop0 kernel: ? do_syscall_64+0x69/0x90
Nov 27 19:21:53 mohanlaptop0 kernel: ? syscall_exit_to_user_mode+0x23/0x50
Nov 27 19:21:53 mohanlaptop0 kernel: ? do_syscall_64+0x69/0x90
Nov 27 19:21:53 mohanlaptop0 kernel: ? syscall_exit_to_user_mode+0x23/0x50
Nov 27 19:21:53 mohanlaptop0 kernel: ? do_syscall_64+0x69/0x90
Nov 27 19:21:53 mohanlaptop0 kernel: ? do_syscall_64+0x69/0x90
Nov 27 19:21:53 mohanlaptop0 kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xae
Thanks,
Mohan R
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Bug using new ntfs3 file system driver (5.15.2 on Arch Linux)
2021-11-27 14:13 Bug using new ntfs3 file system driver (5.15.2 on Arch Linux) Mohan R
@ 2021-11-27 14:50 ` Matthew Wilcox
2021-12-28 21:00 ` August Wikerfors
0 siblings, 1 reply; 8+ messages in thread
From: Matthew Wilcox @ 2021-11-27 14:50 UTC (permalink / raw)
To: Mohan R; +Cc: uwe.sauter.de, almaz.alexandrovich, linux-fsdevel, ntfs3
On Sat, Nov 27, 2021 at 07:43:06PM +0530, Mohan R wrote:
> Hi,
>
> I confirm this issue. I tried to rsync between two ntfs3 mounts, but
> rsync got killed unexpectedly.
This is a completely different problem.
> Nov 27 19:21:53 mohanlaptop0 kernel: BUG: unable to handle page fault
> for address: ffffb9c24fb74000
The address has nothing in common with the address in the original
report.
> Nov 27 19:21:53 mohanlaptop0 kernel: #PF: supervisor read access in kernel mode
> Nov 27 19:21:53 mohanlaptop0 kernel: #PF: error_code(0x0000) - not-present page
> Nov 27 19:21:53 mohanlaptop0 kernel: PGD 100000067 P4D 100000067 PUD
> 1001bd067 PMD 10460a067 PTE 0
> Nov 27 19:21:53 mohanlaptop0 kernel: Oops: 0000 [#2] PREEMPT SMP NOPTI
> Nov 27 19:21:53 mohanlaptop0 kernel: CPU: 5 PID: 144039 Comm: rsync
> Not tainted 5.15.5-arch1-1 #1 f0168f793e3f707b46715a62fafabd6a40826924
> Nov 27 19:21:53 mohanlaptop0 kernel: Hardware name: Dell Inc. Inspiron
> 14 5410/0CKN95, BIOS 2.2.1 07/27/2021
> Nov 27 19:21:53 mohanlaptop0 kernel: RIP: 0010:show_trace_log_lvl+0x1a4/0x32d
> Nov 27 19:21:53 mohanlaptop0 kernel: Code: c7 14 60 a5 86 e8 0f be 00
> 00 4d 85 ed 74 41 0f b6 95 37 ff ff ff 4c 89 f1 4c 89 ee 48 8d bd 50
> ff ff ff e8 dc fd ff ff eb 26 <4c> 8b 3b 48 8d bd 70 ff ff ff e8 2e 4e
> 52 ff 4c 89 ff 48 89 85 28
That's annoying. show_trace_log_lvl() isn't supposed to crash.
> Nov 27 19:21:53 mohanlaptop0 kernel: RSP: 0018:ffffb9c24fb738d8 EFLAGS: 00010012
> Nov 27 19:21:53 mohanlaptop0 kernel: RAX: 0000000000000000 RBX:
> ffffb9c24fb73fff RCX: 0000000000000000
> Nov 27 19:21:53 mohanlaptop0 kernel: RDX: 0000000000000000 RSI:
> 0000000000000000 RDI: 0000000000000000
> Nov 27 19:21:53 mohanlaptop0 kernel: RBP: ffffb9c24fb739b8 R08:
> 0000000000000000 R09: 0000000000000000
> Nov 27 19:21:53 mohanlaptop0 kernel: R10: 0000000000000000 R11:
> 0000000000000000 R12: ffff949c432b0000
> Nov 27 19:21:53 mohanlaptop0 kernel: R13: 0000000000000000 R14:
> ffffffff86a7d25f R15: 0000000000002b00
> Nov 27 19:21:53 mohanlaptop0 kernel: FS: 00007f40259b8580(0000)
> GS:ffff949dc7740000(0000) knlGS:0000000000000000
> Nov 27 19:21:53 mohanlaptop0 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
> 0000000080050033
> Nov 27 19:21:53 mohanlaptop0 kernel: CR2: ffffb9c24fb74000 CR3:
> 00000001b114c005 CR4: 0000000000770ee0
> Nov 27 19:21:53 mohanlaptop0 kernel: PKRU: 55555554
> Nov 27 19:21:53 mohanlaptop0 kernel: Call Trace:
> Nov 27 19:21:53 mohanlaptop0 kernel: <TASK>
> Nov 27 19:21:53 mohanlaptop0 kernel: __die_body.cold+0x1a/0x1f
> Nov 27 19:21:53 mohanlaptop0 kernel: page_fault_oops+0x19e/0x310
> Nov 27 19:21:53 mohanlaptop0 kernel: exc_page_fault+0xda/0x180
> Nov 27 19:21:53 mohanlaptop0 kernel: asm_exc_page_fault+0x1e/0x30
> Nov 27 19:21:53 mohanlaptop0 kernel: RIP: 0010:0xffffff8586d685ff
> Nov 27 19:21:53 mohanlaptop0 kernel: Code: Unable to access opcode
> bytes at RIP 0xffffff8586d685d5.
> Nov 27 19:21:53 mohanlaptop0 kernel: RSP: 0018:ffffb9c24fb73b4f EFLAGS: 00010246
> Nov 27 19:21:53 mohanlaptop0 kernel: RAX: 0000000000000000 RBX:
> 0000000000001700 RCX: 0000000000000000
> Nov 27 19:21:53 mohanlaptop0 kernel: RDX: 0000000000000000 RSI:
> 0000000000000000 RDI: 0000000000000000
> Nov 27 19:21:53 mohanlaptop0 kernel: RBP: ffb9c24fb73c3800 R08:
> 0000000000000000 R09: 0000000000000000
> Nov 27 19:21:53 mohanlaptop0 kernel: R10: 0000000000000000 R11:
> 0000000000000000 R12: ff949b43a8426800
> Nov 27 19:21:53 mohanlaptop0 kernel: R13: 00000001112ccaff R14:
> fff6a0c99d400000 R15: 00000000000056ff
This is where the real bug happened. It would be helpful if you
could run
./scripts/faddr2line /path/to/vmlinux page_cache_ra_unbounded+0x1c5/0x250
It'll spit out something like:
page_cache_ra_unbounded at mm/readahead.c:241
but probably a different line number from that.
> Nov 27 19:21:53 mohanlaptop0 kernel: ? page_cache_ra_unbounded+0x1c5/0x250
> Nov 27 19:21:53 mohanlaptop0 kernel: ? filemap_get_pages+0x269/0x730
> Nov 27 19:21:53 mohanlaptop0 kernel: ? filemap_read+0xb9/0x360
> Nov 27 19:21:53 mohanlaptop0 kernel: ? new_sync_read+0x156/0x1f0
> Nov 27 19:21:53 mohanlaptop0 kernel: ? vfs_read+0xff/0x1a0
> Nov 27 19:21:53 mohanlaptop0 kernel: ? ksys_read+0x67/0xf0
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Bug using new ntfs3 file system driver (5.15.2 on Arch Linux)
2021-11-27 14:50 ` Matthew Wilcox
@ 2021-12-28 21:00 ` August Wikerfors
2021-12-29 1:13 ` Matthew Wilcox
0 siblings, 1 reply; 8+ messages in thread
From: August Wikerfors @ 2021-12-28 21:00 UTC (permalink / raw)
To: Matthew Wilcox
Cc: Mohan R, uwe.sauter.de, almaz.alexandrovich, linux-fsdevel, ntfs3
(resending from gmail due to bounce with outlook)
Hi, I ran into a bug with a very similar call trace, also when copying files
with rsync from a filesystem mounted using ntfs3. I was able to reproduce it
on both the default Arch Linux kernel (5.15.11-arch2-1) and on mainline
5.16-rc7.
> This is where the real bug happened. It would be helpful if you
> could run
> ./scripts/faddr2line /path/to/vmlinux page_cache_ra_unbounded+0x1c5/0x250
>
> It'll spit out something like:
> page_cache_ra_unbounded at mm/readahead.c:241
>
> but probably a different line number from that.
I had to rebuild the vmlinux of my kernels in order for this to work but the
output for the page_cache_ra_unbounded line is below the dmesg outputs.
5.15.11-arch2-1 dmesg:
[ 486.360050] BUG: unable to handle page fault for address: ffffff8306d925ff
[ 486.360083] #PF: supervisor instruction fetch in kernel mode
[ 486.360113] #PF: error_code(0x0010) - not-present page
[ 486.360142] PGD 171815067 P4D 171815067 PUD 0
[ 486.360160] Oops: 0010 [#1] PREEMPT SMP PTI
[ 486.360177] CPU: 2 PID: 1129 Comm: rsync Tainted: G OE
5.15.11-arch2-1 #1 03010ffba27108079ccfa4d61c5b01422e5fb7c7
[ 486.360216] Hardware name: ASUSTeK COMPUTER INC. S551LN/S551LN,
BIOS S551LN.209 07/08/2014
[ 486.360243] RIP: 0010:0xffffff8306d925ff
[ 486.360260] Code: Unable to access opcode bytes at RIP 0xffffff8306d925d5.
[ 486.360302] RSP: 0018:ffffaa9ec0f8fb37 EFLAGS: 00010246
[ 486.360322] RAX: 0000000000000000 RBX: 00000000000002ab RCX: 0000000000000000
[ 486.360355] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 486.360389] RBP: ffaa9ec0f8fbf800 R08: 0000000000000000 R09: 0000000000000000
[ 486.360413] R10: 0000000000000000 R11: 0000000000000000 R12: ff99687f5746e000
[ 486.360456] R13: 00000001112ccaff R14: fffcbb8097368000 R15: 00000000000001ff
[ 486.360481] FS: 00007f9a38011580(0000) GS:ffff9968a6f00000(0000)
knlGS:0000000000000000
[ 486.360509] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 486.360529] CR2: ffffff8306d925d5 CR3: 000000013e140001 CR4: 00000000001706e0
[ 486.360553] Call Trace:
[ 486.360564] <TASK>
[ 486.360584] BUG: unable to handle page fault for address: ffffaa9ec0f90000
[ 486.360608] #PF: supervisor read access in kernel mode
[ 486.360626] #PF: error_code(0x0000) - not-present page
[ 486.360644] PGD 100000067 P4D 100000067 PUD 1001be067 PMD 10ed20067 PTE 0
[ 486.360669] Oops: 0000 [#2] PREEMPT SMP PTI
[ 486.360685] CPU: 2 PID: 1129 Comm: rsync Tainted: G OE
5.15.11-arch2-1 #1 03010ffba27108079ccfa4d61c5b01422e5fb7c7
[ 486.360723] Hardware name: ASUSTeK COMPUTER INC. S551LN/S551LN,
BIOS S551LN.209 07/08/2014
[ 486.360769] RIP: 0010:show_trace_log_lvl+0x1a4/0x32d
[ 486.360789] Code: c7 c4 64 25 84 e8 0f be 00 00 4d 85 ed 74 41 0f
b6 95 37 ff ff ff 4c 89 f1 4c 89 ee 48 8d bd 50 ff ff ff e8 dc fd ff
ff eb 26 <4c> 8b 3b 48 8d bd 70 ff ff ff e8 2e 2e 52 ff 4c 89 ff 48 89
85 28
[ 486.360866] RSP: 0018:ffffaa9ec0f8f8c8 EFLAGS: 00010012
[ 486.360885] RAX: 0000000000000000 RBX: ffffaa9ec0f8ffff RCX: 0000000000000000
[ 486.360910] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 486.360934] RBP: ffffaa9ec0f8f9a8 R08: 0000000000000000 R09: 0000000000000000
[ 486.360958] R10: 0000000000000000 R11: 0000000000000000 R12: ffff9967a2801fc0
[ 486.360983] R13: 0000000000000000 R14: ffffffff8427d77f R15: 0000000000002b00
[ 486.361006] FS: 00007f9a38011580(0000) GS:ffff9968a6f00000(0000)
knlGS:0000000000000000
[ 486.361033] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 486.361053] CR2: ffffaa9ec0f90000 CR3: 000000013e140001 CR4: 00000000001706e0
[ 486.361077] Call Trace:
[ 486.361087] <TASK>
[ 486.361098] __die_body.cold+0x1a/0x1f
[ 486.361114] page_fault_oops+0x19e/0x310
[ 486.361142] exc_page_fault+0xda/0x180
[ 486.361159] asm_exc_page_fault+0x1e/0x30
[ 486.361177] RIP: 0010:0xffffff8306d925ff
[ 486.361192] Code: Unable to access opcode bytes at RIP 0xffffff8306d925d5.
[ 486.361214] RSP: 0018:ffffaa9ec0f8fb37 EFLAGS: 00010246
[ 486.361232] RAX: 0000000000000000 RBX: 00000000000002ab RCX: 0000000000000000
[ 486.361255] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 486.361279] RBP: ffaa9ec0f8fbf800 R08: 0000000000000000 R09: 0000000000000000
[ 486.361302] R10: 0000000000000000 R11: 0000000000000000 R12: ff99687f5746e000
[ 486.361324] R13: 00000001112ccaff R14: fffcbb8097368000 R15: 00000000000001ff
[ 486.361349] ? page_cache_ra_unbounded+0x1c5/0x250
[ 486.361369] ? filemap_get_pages+0x117/0x730
[ 486.361386] ? make_kuid+0xf/0x20
[ 486.361401] ? generic_permission+0x27/0x210
[ 486.361419] ? walk_component+0x11d/0x1c0
[ 486.361435] ? filemap_read+0xb9/0x360
[ 486.361451] ? new_sync_read+0x159/0x1f0
[ 486.361467] ? vfs_read+0xff/0x1a0
[ 486.361489] ? ksys_read+0x67/0xf0
[ 486.361503] ? do_syscall_64+0x5c/0x90
[ 486.361517] ? __audit_syscall_exit+0x255/0x2c0
[ 486.361533] ? syscall_exit_to_user_mode+0x23/0x50
[ 486.362508] ? do_syscall_64+0x69/0x90
[ 486.363455] ? do_syscall_64+0x69/0x90
[ 486.364401] ? do_syscall_64+0x69/0x90
[ 486.365322] ? entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 486.366263] </TASK>
[ 486.367197] Modules linked in: 8021q garp mrp stp llc nls_iso8859_1
vfat fat uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2
videobuf2_common videodev mc x86_pkg_temp_thermal intel_powerclamp
mt76x0e snd_hda_codec_realtek coretemp snd_hda_codec_generic
ledtrig_audio rtsx_usb_ms snd_hda_codec_hdmi memstick kvm_intel
mt76x0_common ntfs3 snd_hda_intel kvm mt76x02_lib joydev asus_nb_wmi
intel_spi_platform intel_spi spi_nor asus_wmi mt76 mtd mousedev
iTCO_wdt snd_intel_dspcfg sparse_keymap intel_pmc_bxt mei_hdcp
intel_rapl_msr iTCO_vendor_support at24 irqbypass platform_profile
mxm_wmi mac80211 snd_intel_sdw_acpi snd_hda_codec snd_hda_core
crct10dif_pclmul i915 crc32_pclmul r8169 snd_hwdep libarc4 cfg80211
snd_pcm ghash_clmulni_intel aesni_intel crypto_simd snd_timer rfkill
realtek cryptd mdio_devres processor_thermal_device_pci_legacy libphy
rapl processor_thermal_device intel_cstate snd pcspkr
processor_thermal_rfim processor_thermal_mbox intel_uncore
processor_thermal_rapl
[ 486.367240] mei_me intel_rapl_common soundcore ttm mei
intel_soc_dts_iosf intel_gtt video lpc_ich i2c_i801 int3402_thermal
i2c_smbus intel_pch_thermal psmouse int3400_thermal
int340x_thermal_zone wmi acpi_thermal_rel asus_wireless mac_hid
vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) crypto_user fuse bpf_preload
ip_tables x_tables btrfs blake2b_generic libcrc32c crc32c_generic xor
raid6_pq rtsx_usb_sdmmc mmc_core rtsx_usb serio_raw atkbd libps2
crc32c_intel xhci_pci sr_mod i8042 cdrom xhci_pci_renesas serio
[ 486.376305] CR2: ffffaa9ec0f90000
[ 486.377512] ---[ end trace 2b657e7ade0f9e60 ]---
[ 486.378748] RIP: 0010:0xffffff8306d925ff
[ 486.380001] Code: Unable to access opcode bytes at RIP 0xffffff8306d925d5.
[ 486.381220] RSP: 0018:ffffaa9ec0f8fb37 EFLAGS: 00010246
[ 486.382432] RAX: 0000000000000000 RBX: 00000000000002ab RCX: 0000000000000000
[ 486.383656] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 486.384871] RBP: ffaa9ec0f8fbf800 R08: 0000000000000000 R09: 0000000000000000
[ 486.386072] R10: 0000000000000000 R11: 0000000000000000 R12: ff99687f5746e000
[ 486.387278] R13: 00000001112ccaff R14: fffcbb8097368000 R15: 00000000000001ff
[ 486.388478] FS: 00007f9a38011580(0000) GS:ffff9968a6f00000(0000)
knlGS:0000000000000000
[ 486.389684] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 486.390890] CR2: ffffff8306d925d5 CR3: 000000013e140001 CR4: 00000000001706e0
$ scripts/faddr2line vmlinux.5.15.11-arch2-1 page_cache_ra_unbounded+0x1c5/0x250
page_cache_ra_unbounded+0x1c5/0x250:
filemap_invalidate_unlock_shared at include/linux/fs.h:853
(inlined by) page_cache_ra_unbounded at mm/readahead.c:240
5.16-rc7 dmesg:
[ 258.570806] ------------[ cut here ]------------
[ 258.570810] kernel BUG at mm/readahead.c:151!
[ 258.570817] invalid opcode: 0000 [#1] PREEMPT SMP PTI
[ 258.570822] CPU: 0 PID: 1136 Comm: rsync Not tainted
5.16.0-rc7-1-mainline #1 b49cff4185a0eb169c9f956a386eb3a9156e4796
[ 258.570827] Hardware name: ASUSTeK COMPUTER INC. S551LN/S551LN,
BIOS S551LN.209 07/08/2014
[ 258.570829] RIP: 0010:read_pages+0x26c/0x280
[ 258.570836] Code: eb 87 48 8b 07 48 c1 e8 38 83 e0 07 83 f8 04 75
e4 48 8b 47 08 8b 40 68 83 e8 01 83 f8 01 77 d5 e8 39 18 00 00 e9 5f
ff ff ff <0f> 0b 0f 0b e8 bb 4d 96 00 66 66 2e 0f 1f 84 00 00 00 00 00
0f 1f
[ 258.570838] RSP: 0018:ffff9d59c0b1fa78 EFLAGS: 00010206
[ 258.570842] RAX: ff9d59c0b1fb1000 RBX: ffff9d59c0b1fbc0 RCX: 0000000000000000
[ 258.570844] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 258.570846] RBP: ffff9d59c0b1fb0f R08: 0000000000000000 R09: 0000000000000000
[ 258.570848] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 258.570850] R13: 0000000000000000 R14: ffffc4ba4632d680 R15: 0000000000000002
[ 258.570852] FS: 00007f9a9ec98580(0000) GS:ffff8b9f26e00000(0000)
knlGS:0000000000000000
[ 258.570855] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 258.570857] CR2: 00005646e709b000 CR3: 00000001361ee005 CR4: 00000000001706f0
[ 258.570860] Call Trace:
[ 258.570862] <TASK>
[ 258.570865] page_cache_ra_unbounded+0x1d9/0x270
[ 258.570872] filemap_get_pages+0x11e/0x7e0
[ 258.570878] ? generic_permission+0x27/0x210
[ 258.570885] ? walk_component+0x11d/0x1c0
[ 258.570891] filemap_read+0xcc/0x380
[ 258.570897] new_sync_read+0x159/0x1f0
[ 258.570902] vfs_read+0xff/0x1a0
[ 258.570907] ksys_read+0x67/0xf0
[ 258.570911] do_syscall_64+0x5c/0x90
[ 258.570919] ? syscall_exit_to_user_mode+0x23/0x50
[ 258.570923] ? do_syscall_64+0x69/0x90
[ 258.570927] ? exit_to_user_mode_prepare+0x8d/0x180
[ 258.570932] ? syscall_exit_to_user_mode+0x23/0x50
[ 258.570935] ? do_syscall_64+0x69/0x90
[ 258.570938] ? do_syscall_64+0x69/0x90
[ 258.570942] ? do_syscall_64+0x69/0x90
[ 258.570946] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 258.570951] RIP: 0033:0x7f9a9edb0862
[ 258.570954] Code: c0 e9 b2 fe ff ff 50 48 8d 3d 5a 29 0a 00 e8 55
e4 01 00 0f 1f 44 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75
10 0f 05 <48> 3d 00 f0 ff ff 77 56 c3 0f 1f 44 00 00 48 83 ec 28 48 89
54 24
[ 258.570957] RSP: 002b:00007ffdd97ee518 EFLAGS: 00000246 ORIG_RAX:
0000000000000000
[ 258.570960] RAX: ffffffffffffffda RBX: 00005646e6850640 RCX: 00007f9a9edb0862
[ 258.570962] RDX: 000000000000219e RSI: 00005646e6f1cab0 RDI: 0000000000000003
[ 258.570964] RBP: 000000000000219e R08: 0000000000000000 R09: 00007f9a9ee81a60
[ 258.570966] R10: 00007f9a9ee821b0 R11: 0000000000000246 R12: 0000000000000000
[ 258.570968] R13: 0000000000000000 R14: 0000000000000000 R15: 000000000000219e
[ 258.570971] </TASK>
[ 258.570972] Modules linked in: 8021q garp mrp stp llc nls_iso8859_1
vfat fat uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2
videobuf2_common videodev mc ntfs3 intel_spi_platform intel_spi
x86_pkg_temp_thermal spi_nor intel_powerclamp mtd
snd_hda_codec_realtek rtsx_usb_ms coretemp iTCO_wdt
snd_hda_codec_generic memstick intel_pmc_bxt snd_hda_codec_hdmi
kvm_intel iTCO_vendor_support ledtrig_audio kvm joydev mousedev at24
asus_nb_wmi intel_rapl_msr mei_hdcp asus_wmi mt76x0e sparse_keymap
platform_profile irqbypass crct10dif_pclmul snd_hda_intel
mt76x0_common snd_intel_dspcfg crc32_pclmul mt76x02_lib
ghash_clmulni_intel aesni_intel mt76 crypto_simd snd_intel_sdw_acpi
mac80211 snd_hda_codec libarc4 cfg80211 cryptd snd_hda_core rfkill
r8169 rapl intel_cstate realtek intel_uncore mxm_wmi mdio_devres
libphy i915 processor_thermal_device_pci_legacy
processor_thermal_device processor_thermal_rfim snd_hwdep i2c_i801
processor_thermal_mbox snd_pcm snd_timer processor_thermal_rapl mei_me
[ 258.571036] video mei i2c_smbus ttm lpc_ich intel_rapl_common snd
intel_gtt intel_pch_thermal soundcore mac_hid intel_soc_dts_iosf
psmouse pcspkr int3400_thermal wmi int3402_thermal acpi_thermal_rel
int340x_thermal_zone asus_wireless crypto_user fuse bpf_preload
ip_tables x_tables btrfs blake2b_generic libcrc32c crc32c_generic xor
raid6_pq rtsx_usb_sdmmc mmc_core rtsx_usb serio_raw atkbd libps2
xhci_pci crc32c_intel sr_mod i8042 cdrom xhci_pci_renesas serio
[ 258.571071] ---[ end trace 685ffdce3faf85b7 ]---
[ 258.571073] RIP: 0010:read_pages+0x26c/0x280
[ 258.571077] Code: eb 87 48 8b 07 48 c1 e8 38 83 e0 07 83 f8 04 75
e4 48 8b 47 08 8b 40 68 83 e8 01 83 f8 01 77 d5 e8 39 18 00 00 e9 5f
ff ff ff <0f> 0b 0f 0b e8 bb 4d 96 00 66 66 2e 0f 1f 84 00 00 00 00 00
0f 1f
[ 258.571079] RSP: 0018:ffff9d59c0b1fa78 EFLAGS: 00010206
[ 258.571081] RAX: ff9d59c0b1fb1000 RBX: ffff9d59c0b1fbc0 RCX: 0000000000000000
[ 258.571083] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 258.571085] RBP: ffff9d59c0b1fb0f R08: 0000000000000000 R09: 0000000000000000
[ 258.571087] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 258.571088] R13: 0000000000000000 R14: ffffc4ba4632d680 R15: 0000000000000002
[ 258.571090] FS: 00007f9a9ec98580(0000) GS:ffff8b9f26e00000(0000)
knlGS:0000000000000000
[ 258.571093] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 258.571095] CR2: 00005646e709b000 CR3: 00000001361ee005 CR4: 00000000001706f0
$ scripts/faddr2line vmlinux.5.16.0-rc7-1-mainline
page_cache_ra_unbounded+0x1d9/0x270
page_cache_ra_unbounded+0x1d9/0x270:
filemap_invalidate_unlock_shared at include/linux/fs.h:850
(inlined by) page_cache_ra_unbounded at mm/readahead.c:239
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Bug using new ntfs3 file system driver (5.15.2 on Arch Linux)
2021-12-28 21:00 ` August Wikerfors
@ 2021-12-29 1:13 ` Matthew Wilcox
2022-01-03 15:20 ` Jan Kara
0 siblings, 1 reply; 8+ messages in thread
From: Matthew Wilcox @ 2021-12-29 1:13 UTC (permalink / raw)
To: August Wikerfors
Cc: Mohan R, uwe.sauter.de, almaz.alexandrovich, linux-fsdevel, ntfs3,
Jan Kara
On Tue, Dec 28, 2021 at 10:00:53PM +0100, August Wikerfors wrote:
> (resending from gmail due to bounce with outlook)
>
> Hi, I ran into a bug with a very similar call trace, also when copying files
> with rsync from a filesystem mounted using ntfs3. I was able to reproduce it
> on both the default Arch Linux kernel (5.15.11-arch2-1) and on mainline
> 5.16-rc7.
Hi August! This is very helpful; thank you for putting in the work to
figure this out. I am still a little baffled:
> [ 486.361177] RIP: 0010:0xffffff8306d925ff
> [ 486.361192] Code: Unable to access opcode bytes at RIP 0xffffff8306d925d5.
> [ 486.361214] RSP: 0018:ffffaa9ec0f8fb37 EFLAGS: 00010246
> [ 486.361232] RAX: 0000000000000000 RBX: 00000000000002ab RCX: 0000000000000000
> [ 486.361255] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
> [ 486.361279] RBP: ffaa9ec0f8fbf800 R08: 0000000000000000 R09: 0000000000000000
> [ 486.361302] R10: 0000000000000000 R11: 0000000000000000 R12: ff99687f5746e000
> [ 486.361324] R13: 00000001112ccaff R14: fffcbb8097368000 R15: 00000000000001ff
> [ 486.361349] ? page_cache_ra_unbounded+0x1c5/0x250
> [ 486.361369] ? filemap_get_pages+0x117/0x730
> [ 486.361386] ? make_kuid+0xf/0x20
> [ 486.361401] ? generic_permission+0x27/0x210
> [ 486.361419] ? walk_component+0x11d/0x1c0
> [ 486.361435] ? filemap_read+0xb9/0x360
> [ 486.361451] ? new_sync_read+0x159/0x1f0
> [ 486.361467] ? vfs_read+0xff/0x1a0
> [ 486.361489] ? ksys_read+0x67/0xf0
> [ 486.361503] ? do_syscall_64+0x5c/0x90
>
> $ scripts/faddr2line vmlinux.5.15.11-arch2-1 page_cache_ra_unbounded+0x1c5/0x250
> page_cache_ra_unbounded+0x1c5/0x250:
> filemap_invalidate_unlock_shared at include/linux/fs.h:853
> (inlined by) page_cache_ra_unbounded at mm/readahead.c:240
So ... Jan added this code in commit 730633f0b7f9, but I don't see how
it could be buggy:
filemap_invalidate_lock_shared(mapping);
... things that don't change mapping ...
filemap_invalidate_unlock_shared(mapping);
and the _unlock_ appears to have a bad pointer. Which makes no sense
to me. Jan, any ideas?
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: Bug using new ntfs3 file system driver (5.15.2 on Arch Linux)
2021-12-29 1:13 ` Matthew Wilcox
@ 2022-01-03 15:20 ` Jan Kara
0 siblings, 0 replies; 8+ messages in thread
From: Jan Kara @ 2022-01-03 15:20 UTC (permalink / raw)
To: Matthew Wilcox
Cc: August Wikerfors, Mohan R, uwe.sauter.de, almaz.alexandrovich,
linux-fsdevel, ntfs3, Jan Kara
On Wed 29-12-21 01:13:20, Matthew Wilcox wrote:
> On Tue, Dec 28, 2021 at 10:00:53PM +0100, August Wikerfors wrote:
> > (resending from gmail due to bounce with outlook)
> >
> > Hi, I ran into a bug with a very similar call trace, also when copying files
> > with rsync from a filesystem mounted using ntfs3. I was able to reproduce it
> > on both the default Arch Linux kernel (5.15.11-arch2-1) and on mainline
> > 5.16-rc7.
>
> Hi August! This is very helpful; thank you for putting in the work to
> figure this out. I am still a little baffled:
>
> > [ 486.361177] RIP: 0010:0xffffff8306d925ff
> > [ 486.361192] Code: Unable to access opcode bytes at RIP 0xffffff8306d925d5.
> > [ 486.361214] RSP: 0018:ffffaa9ec0f8fb37 EFLAGS: 00010246
> > [ 486.361232] RAX: 0000000000000000 RBX: 00000000000002ab RCX: 0000000000000000
> > [ 486.361255] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
> > [ 486.361279] RBP: ffaa9ec0f8fbf800 R08: 0000000000000000 R09: 0000000000000000
> > [ 486.361302] R10: 0000000000000000 R11: 0000000000000000 R12: ff99687f5746e000
> > [ 486.361324] R13: 00000001112ccaff R14: fffcbb8097368000 R15: 00000000000001ff
> > [ 486.361349] ? page_cache_ra_unbounded+0x1c5/0x250
> > [ 486.361369] ? filemap_get_pages+0x117/0x730
> > [ 486.361386] ? make_kuid+0xf/0x20
> > [ 486.361401] ? generic_permission+0x27/0x210
> > [ 486.361419] ? walk_component+0x11d/0x1c0
> > [ 486.361435] ? filemap_read+0xb9/0x360
> > [ 486.361451] ? new_sync_read+0x159/0x1f0
> > [ 486.361467] ? vfs_read+0xff/0x1a0
> > [ 486.361489] ? ksys_read+0x67/0xf0
> > [ 486.361503] ? do_syscall_64+0x5c/0x90
> >
> > $ scripts/faddr2line vmlinux.5.15.11-arch2-1 page_cache_ra_unbounded+0x1c5/0x250
> > page_cache_ra_unbounded+0x1c5/0x250:
> > filemap_invalidate_unlock_shared at include/linux/fs.h:853
> > (inlined by) page_cache_ra_unbounded at mm/readahead.c:240
>
> So ... Jan added this code in commit 730633f0b7f9, but I don't see how
> it could be buggy:
I don't think the problem is with my code. The address
page_cache_ra_unbounded+0x1c5/0x250 is from the stack which means it is a
return address for the function that's currently executing or just to be
called - presumably from read_pages(). And note that we crashed because we
tried to call / jump to invalid address. So most likely aops->readpage(),
aops->readahead(), or aops->readpages() was the bogus address
0xffffff8306d925d5. How it got there I don't know but I'd closely look into
the ntfs3 driver...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
^ permalink raw reply [flat|nested] 8+ messages in thread
* Bug using new ntfs3 file system driver (5.15.2 on Arch Linux)
@ 2021-11-19 7:48 Uwe Sauter
2021-11-19 13:13 ` Matthew Wilcox
0 siblings, 1 reply; 8+ messages in thread
From: Uwe Sauter @ 2021-11-19 7:48 UTC (permalink / raw)
To: almaz.alexandrovich, ntfs3, linux-fsdevel
Dear devs and maintainers,
during the first heavy usage of the new ntfs3 driver I experienced the following kernel bug.
I wanted to rsync several GB from a NTFS file system stored on a ZFS volume to another NTFS file system on a plain
partition.
Both drives were connected to a SAS controller (LSISAS2008, mpt2sas). The host has ECC memory.
After this bug I remounted both file systems using the FUSE NTFS-3g driver and sync'd the data without problems.
I'm not sure if this really is ntfs3 related but being the most prominent change in my workflow, this is my best bet.
Thanks for your work,
Uwe Sauter
#### snip ####
[ 1132.645038] BUG: unable to handle page fault for address: 0000000000400000
[ 1132.645045] #PF: supervisor instruction fetch in kernel mode
[ 1132.645047] #PF: error_code(0x0010) - not-present page
[ 1132.645050] PGD 0 P4D 0
[ 1132.645053] Oops: 0010 [#1] PREEMPT SMP PTI
[ 1132.645057] CPU: 7 PID: 429941 Comm: rsync Tainted: P OE 5.15.2-arch1-1 #1
e3bfbeb633edc604ba956e06f24d5659e31c294f
[ 1132.645061] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./C226 WS, BIOS P3.40 06/25/2018
[ 1132.645063] RIP: 0010:0x400000
[ 1132.645067] Code: Unable to access opcode bytes at RIP 0x3fffd6.
[ 1132.645068] RSP: 0018:ffffac7e63a7fab8 EFLAGS: 00010246
[ 1132.645071] RAX: 0000000000000000 RBX: ffff95e55b7e3f80 RCX: 0000000000000000
[ 1132.645074] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 1132.645075] RBP: ffff95e55b7e3f80 R08: 0000000000000000 R09: 0000000000000000
[ 1132.645077] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002
[ 1132.645079] R13: ffffac7e63a7fb30 R14: ffffee3e0e250380 R15: ffffffffb4e09158
[ 1132.645081] FS: 00007fa8065b7580(0000) GS:ffff95ec003c0000(0000) knlGS:0000000000000000
[ 1132.645084] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1132.645086] CR2: 0000000000400000 CR3: 0000000264e28002 CR4: 00000000001706e0
[ 1132.645089] Call Trace:
[ 1132.645093] ? io_schedule+0x42/0x70
[ 1132.645100] ? wait_on_page_bit_common+0x10d/0x3c0
[ 1132.645105] ? __page_cache_alloc+0x90/0x90
[ 1132.645109] ? filemap_get_pages+0x6ed/0x730
[ 1132.645113] ? filemap_read+0xb9/0x360
[ 1132.645117] ? pty_write+0x8e/0x90
[ 1132.645123] ? new_sync_read+0x159/0x1f0
[ 1132.645128] ? vfs_read+0xff/0x1a0
[ 1132.645131] ? ksys_read+0x67/0xf0
[ 1132.645135] ? do_syscall_64+0x5c/0x90
[ 1132.645140] ? ksys_write+0x67/0xf0
[ 1132.645143] ? syscall_exit_to_user_mode+0x23/0x50
[ 1132.645146] ? do_syscall_64+0x69/0x90
[ 1132.645150] ? syscall_exit_to_user_mode+0x23/0x50
[ 1132.645153] ? do_syscall_64+0x69/0x90
[ 1132.645156] ? exit_to_user_mode_prepare+0x12d/0x180
[ 1132.645161] ? syscall_exit_to_user_mode+0x23/0x50
[ 1132.645163] ? __x64_sys_close+0xd/0x50
[ 1132.645168] ? do_syscall_64+0x69/0x90
[ 1132.645171] ? do_syscall_64+0x69/0x90
[ 1132.645174] ? do_syscall_64+0x69/0x90
[ 1132.645178] ? entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 1132.645183] Modules linked in: ntfs3 dm_mod vhost_net vhost vhost_iotlb tap tun xt_MASQUERADE xt_CHECKSUM
ip6table_mangle iptable_mangle bridge stp llc ip6table_nat ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables
iptable_nat nf_nat ipt_REJECT nf_reject_ipv4 xt_multiport xt_tcpudp xt_state xt_conntrack nf_conntrack nf_defrag_ipv6
nf_defrag_ipv4 libcrc32c crc32c_generic iptable_filter rpcrdma sunrpc rdma_ucm ib_iser libiscsi scsi_transport_iscsi
ib_umad rdma_cm ib_ipoib iw_cm ib_cm mlx4_en mlx4_ib ib_uverbs ib_core intel_rapl_msr intel_rapl_common
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel tda18212 cxd2841er kvm irqbypass snd_hda_codec_realtek
snd_ice1712 crct10dif_pclmul snd_hda_codec_generic snd_cs8427 iTCO_wdt intel_spi_platform intel_spi ledtrig_audio
crc32_pclmul crc32c_intel snd_i2c spi_nor snd_ice17xx_ak4xxx snd_hda_intel intel_pmc_bxt ddbridge ghash_clmulni_intel
snd_ak4xxx_adda at24 mtd iTCO_vendor_support mei_hdcp snd_intel_dspcfg snd_ac97_codec aesni_intel
[ 1132.645256] snd_intel_sdw_acpi dvb_core crypto_simd videobuf2_vmalloc snd_hda_codec snd_mpu401_uart cryptd
snd_rawmidi videobuf2_memops rapl snd_hda_core snd_seq_device intel_cstate ac97_bus intel_uncore snd_hwdep
videobuf2_common pcspkr snd_pcm i2c_i801 videodev snd_timer i2c_smbus joydev mousedev mc igb lpc_ich mei_me snd dca
mlx4_core mei soundcore ie31200_edac mac_hid acpi_pad vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) sg crypto_user fuse
bpf_preload ip_tables x_tables hid_microsoft ff_memless usbhid raid1 md_mod xhci_pci xhci_pci_renesas zfs(POE)
zunicode(POE) zzstd(OE) zlua(OE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) mpt3sas raid_class
scsi_transport_sas i915 video ttm intel_agp intel_gtt
[ 1132.645320] CR2: 0000000000400000
[ 1132.645323] ---[ end trace 08a4d6a7ac863916 ]---
[ 1132.648651] RIP: 0010:0x400000
[ 1132.648654] Code: Unable to access opcode bytes at RIP 0x3fffd6.
[ 1132.648655] RSP: 0018:ffffac7e63a7fab8 EFLAGS: 00010246
[ 1132.648657] RAX: 0000000000000000 RBX: ffff95e55b7e3f80 RCX: 0000000000000000
[ 1132.648658] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 1132.648659] RBP: ffff95e55b7e3f80 R08: 0000000000000000 R09: 0000000000000000
[ 1132.648660] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002
[ 1132.648661] R13: ffffac7e63a7fb30 R14: ffffee3e0e250380 R15: ffffffffb4e09158
[ 1132.648662] FS: 00007fa8065b7580(0000) GS:ffff95ec003c0000(0000) knlGS:0000000000000000
[ 1132.648663] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1132.648676] CR2: 0000000000400000 CR3: 0000000264e28002 CR4: 00000000001706e0
[ 1132.648678] note: rsync[429941] exited with preempt_count 1
#### snap ####
#### Environment ####
Arch Linux with packages:
linux 5.15.2.arch1-1
ntfs-3g 2021.8.22-1
zfs-linux-git 2021.11.13.r7179.g8ac58c3f56_5.15.2.arch1.1-1
zfs-utils-git 2021.11.13.r7179.g8ac58c3f56-1
rsync 3.2.3-4
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Bug using new ntfs3 file system driver (5.15.2 on Arch Linux)
2021-11-19 7:48 Uwe Sauter
@ 2021-11-19 13:13 ` Matthew Wilcox
2021-11-19 14:19 ` Uwe Sauter
0 siblings, 1 reply; 8+ messages in thread
From: Matthew Wilcox @ 2021-11-19 13:13 UTC (permalink / raw)
To: Uwe Sauter; +Cc: almaz.alexandrovich, ntfs3, linux-fsdevel
On Fri, Nov 19, 2021 at 08:48:11AM +0100, Uwe Sauter wrote:
> [ 1132.645038] BUG: unable to handle page fault for address: 0000000000400000
> [ 1132.645045] #PF: supervisor instruction fetch in kernel mode
> [ 1132.645047] #PF: error_code(0x0010) - not-present page
> [ 1132.645050] PGD 0 P4D 0
> [ 1132.645053] Oops: 0010 [#1] PREEMPT SMP PTI
> [ 1132.645057] CPU: 7 PID: 429941 Comm: rsync Tainted: P OE
> 5.15.2-arch1-1 #1 e3bfbeb633edc604ba956e06f24d5659e31c294f
> [ 1132.645061] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./C226 WS, BIOS P3.40 06/25/2018
> [ 1132.645063] RIP: 0010:0x400000
Your computer was trying to execute instructions at 0x400000. This
smells very much like a single bit flip; ie there was a function
pointer which should have been NULL, but actually had one bit flip
and so the CPU jumped to somewhere that doesn't have any memory
backing it.
Can you run memtest86, or whatever the current flavour of memory testing
software is?
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Bug using new ntfs3 file system driver (5.15.2 on Arch Linux)
2021-11-19 13:13 ` Matthew Wilcox
@ 2021-11-19 14:19 ` Uwe Sauter
0 siblings, 0 replies; 8+ messages in thread
From: Uwe Sauter @ 2021-11-19 14:19 UTC (permalink / raw)
To: Matthew Wilcox; +Cc: almaz.alexandrovich, ntfs3, linux-fsdevel
Am 19.11.21 um 14:13 schrieb Matthew Wilcox:
> On Fri, Nov 19, 2021 at 08:48:11AM +0100, Uwe Sauter wrote:
>> [ 1132.645038] BUG: unable to handle page fault for address: 0000000000400000
>> [ 1132.645045] #PF: supervisor instruction fetch in kernel mode
>> [ 1132.645047] #PF: error_code(0x0010) - not-present page
>> [ 1132.645050] PGD 0 P4D 0
>> [ 1132.645053] Oops: 0010 [#1] PREEMPT SMP PTI
>> [ 1132.645057] CPU: 7 PID: 429941 Comm: rsync Tainted: P OE
>> 5.15.2-arch1-1 #1 e3bfbeb633edc604ba956e06f24d5659e31c294f
>> [ 1132.645061] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./C226 WS, BIOS P3.40 06/25/2018
>> [ 1132.645063] RIP: 0010:0x400000
>
> Your computer was trying to execute instructions at 0x400000. This
> smells very much like a single bit flip; ie there was a function
> pointer which should have been NULL, but actually had one bit flip
> and so the CPU jumped to somewhere that doesn't have any memory
> backing it.
>
> Can you run memtest86, or whatever the current flavour of memory testing
> software is?
>
As I mentioned in the description the host is equipped with ECC memory. dmesg didn't show any sign of memory error that
I would expect from a bit flip inside RAM.
The hardware is
* ASRock Rack C226 WS mainboard
* Intel Xeon E3-1245 v3
* 4x Kingston 9965525-055.A00LF 8GB ECC memory.
Also the host has been running fine after the bug triggered for 1.5h and today again for 7h.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2022-01-06 15:46 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-11-27 14:13 Bug using new ntfs3 file system driver (5.15.2 on Arch Linux) Mohan R
2021-11-27 14:50 ` Matthew Wilcox
2021-12-28 21:00 ` August Wikerfors
2021-12-29 1:13 ` Matthew Wilcox
2022-01-03 15:20 ` Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2021-11-19 7:48 Uwe Sauter
2021-11-19 13:13 ` Matthew Wilcox
2021-11-19 14:19 ` Uwe Sauter
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).