From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 217266] kernel panic on f2fs filesystem when f2fs_commit_atomic_write
Date: Wed, 29 Mar 2023 17:58:36 +0000 [thread overview]
Message-ID: <bug-217266-202145-g69mVLk97s@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217266-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217266
--- Comment #1 from michalechner92@googlemail.com ---
That looks identical to what I reported last week here:
https://sourceforge.net/p/linux-f2fs/mailman/message/37794257/
Am Mi., 29. März 2023 um 09:02 Uhr schrieb <bugzilla-daemon@kernel.org>:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=217266
>
> Bug ID: 217266
> Summary: kernel panic on f2fs filesystem when
> f2fs_commit_atomic_write
> Product: File System
> Version: 2.5
> Kernel Version: 6.2.8
> Hardware: Intel
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: blocking
> Priority: P1
> Component: f2fs
> Assignee: filesystem_f2fs@kernel-bugs.kernel.org
> Reporter: shilkazx@gmail.com
> Regression: No
>
> Created attachment 304050
> --> https://bugzilla.kernel.org/attachment.cgi?id=304050&action=edit
> system journal
>
> Under daily usage senario, kernel panic occurred.
> OS: Archlinux x64 with kernel 6.2.8-1
> Hardware: Dell XPS 13 7390 laptop
>
> 1 │ Mar 28 18:13:53 shilka kernel: BUG: kernel NULL pointer dereference,
> address: 0000000000000000
> 2 │ Mar 28 18:13:53 shilka kernel: #PF: supervisor read access in kernel
> mode
> 3 │ Mar 28 18:13:53 shilka kernel: #PF: error_code(0x0000) - not-present
> page
> 4 │ Mar 28 18:13:53 shilka kernel: PGD 0 P4D 0
> 5 │ Mar 28 18:13:53 shilka kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
> 6 │ Mar 28 18:13:53 shilka kernel: CPU: 6 PID: 82195 Comm:
> ThreadPoolForeg
> Tainted: G OE 6.2.8-arch1-1 #1
> 97507a85a20085e4c7bd7722b8899840c7d0bffd
> 7 │ Mar 28 18:13:53 shilka kernel: Hardware name: Dell Inc. XPS 13
> 7390/0X2XTG, BIOS 1.17.0 07/11/2022
> 8 │ Mar 28 18:13:53 shilka kernel: RIP:
> 0010:__replace_atomic_write_block+0x184/0x620 [f2fs]
> 9 │ Mar 28 18:13:53 shilka kernel: Code: 74 0b 48 3b 5c 24 38 0f 85 29
> 01
> 00 00 48 8b 04 24 48 8b 95 80 03 00 00 48 c7 44 24 38 00 00 00 00 48 c7 44 24
> 30 00 00 00 00 <44> 8b 00 66 90 48 8b 44 24 58 65 48 2b
> │ 04 25 28 00 00 00 0f 85 7c
> 10 │ Mar 28 18:13:53 shilka kernel: RSP: 0018:ffffb4a246817c80 EFLAGS:
> 00010246
> 11 │ Mar 28 18:13:53 shilka kernel: RAX: 0000000000000000 RBX:
> ffffee060710d500 RCX: 0000000000ec8c06
> 12 │ Mar 28 18:13:53 shilka kernel: RDX: ffff963c72a217e8 RSI:
> 0000000000000001 RDI: ffffee060710d500
> 13 │ Mar 28 18:13:53 shilka kernel: RBP: ffff963ab0333960 R08:
> ffff963aebe108a0 R09: 0000000080380011
> 14 │ Mar 28 18:13:53 shilka kernel: R10: 0000000000000088 R11:
> ffffffffffffffff R12: 0000000000000000
> 15 │ Mar 28 18:13:53 shilka kernel: R13: 00000000010ea75c R14:
> 0000000000000000 R15: ffff963a412e3000
> 16 │ Mar 28 18:13:53 shilka kernel: FS: 00007f68dff0a6c0(0000)
> GS:ffff963dbe780000(0000) knlGS:0000000000000000
> 17 │ Mar 28 18:13:53 shilka kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
> 0000000080050033
> 18 │ Mar 28 18:13:53 shilka kernel: CR2: 0000000000000000 CR3:
> 0000000378db8001 CR4: 00000000003706e0
> 19 │ Mar 28 18:13:53 shilka kernel: Call Trace:
> 20 │ Mar 28 18:13:53 shilka kernel: <TASK>
> 21 │ Mar 28 18:13:53 shilka kernel: f2fs_commit_atomic_write+0x619/0x990
> [f2fs a1b985b80f5babd6f3ea778384908880812bfa43]
> 22 │ Mar 28 18:13:53 shilka kernel: __f2fs_ioctl+0xd8e/0x4080 [f2fs
> a1b985b80f5babd6f3ea778384908880812bfa43]
> 23 │ Mar 28 18:13:53 shilka kernel: ? vfs_write+0x2ae/0x3f0
> 24 │ Mar 28 18:13:53 shilka kernel: ? vfs_write+0x2ae/0x3f0
> 25 │ Mar 28 18:13:53 shilka kernel: __x64_sys_ioctl+0x91/0xd0
> 26 │ Mar 28 18:13:53 shilka kernel: do_syscall_64+0x5c/0x90
> 27 │ Mar 28 18:13:53 shilka kernel:
> entry_SYSCALL_64_after_hwframe+0x72/0xdc
> 28 │ Mar 28 18:13:53 shilka kernel: RIP: 0033:0x7f69095fe53f
> 29 │ Mar 28 18:13:53 shilka kernel: Code: 00 48 89 44 24 18 31 c0 48 8d
> 44
> 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10
> 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24
> │ 18 64 48 2b 04 25 28 00 00
> 30 │ Mar 28 18:13:53 shilka kernel: RSP: 002b:00007f68dff085a0 EFLAGS:
> 00000246 ORIG_RAX: 0000000000000010
> 31 │ Mar 28 18:13:53 shilka kernel: RAX: ffffffffffffffda RBX:
> 000000000000000c RCX: 00007f69095fe53f
> 32 │ Mar 28 18:13:53 shilka kernel: RDX: 0000000000000000 RSI:
> 000000000000f502 RDI: 000000000000004d
> 33 │ Mar 28 18:13:53 shilka kernel: RBP: 00007f68dff08700 R08:
> 00005573b5920960 R09: 00005573b5920a88
> 34 │ Mar 28 18:13:53 shilka kernel: R10: 0000000000368000 R11:
> 0000000000000246 R12: 00000b98003ba800
> 35 │ Mar 28 18:13:53 shilka kernel: R13: 00000b98007da080 R14:
> 0000000000000000 R15: 0000000000000000
> 36 │ Mar 28 18:13:53 shilka kernel: </TASK>
> 37 │ Mar 28 18:13:53 shilka kernel: Modules linked in: nls_utf8 cifs
> cifs_arc4 cifs_md4 dns_resolver fscache netfs rfcomm snd_seq_dummy
> snd_hrtimer
> snd_seq snd_seq_device ccm typec_displayport nf_conntrack_net
> │ bios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4
> nft_fib_ipv6
> nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct
> nft_chain_nat snd_hda_codec_hdmi nf_tables ip6table_nat ip6tab
> │ le_mangle ip6table_raw ip6table_security iptable_nat nf_nat
> nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c crc32c_generic
> iptable_mangle iptable_raw iptable_security nfnetlink ip6table_filter ip6_ta
> │ bles iptable_filter cmac algif_hash algif_skcipher af_alg bnep
> r8153_ecm cdc_ether usbnet tun r8152 mii snd_sof_pci_intel_cnl
> snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation
> soundwir
> │ e_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof
> snd_sof_utils soundwire_bus snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core
> snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match
> 38 │ Mar 28 18:13:53 shilka kernel: snd_soc_acpi x86_pkg_temp_thermal
> intel_powerclamp coretemp snd_soc_core snd_ctl_led kvm_intel snd_compress
> snd_hda_codec_realtek snd_hda_codec_generic ac97_bus snd_pcm_dma
> │ engine kvm iwlmvm snd_hda_intel irqbypass snd_intel_dspcfg
> crct10dif_pclmul btusb mac80211 crc32c_intel joydev btrtl uvcvideo
> snd_intel_sdw_acpi btbcm polyval_clmulni videobuf2_vmalloc polyval_generic
> iTC
> │ O_wdt snd_hda_codec mousedev videobuf2_memops libarc4 gf128mul
> btintel
> processor_thermal_device_pci_legacy dell_laptop intel_pmc_bxt btmtk
> snd_hda_core ghash_clmulni_intel processor_thermal_device videobu
> │ f2_v4l2 dell_wmi hid_multitouch i915 cdc_acm mei_pxp
> iTCO_vendor_support mei_hdcp intel_rapl_msr snd_hwdep processor_thermal_rfim
> sha512_ssse3 bluetooth videodev processor_thermal_mbox snd_pcm dell_smbios
> │ dell_wmi_ddv dell_wmi_sysman aesni_intel drm_buddy iwlwifi
> intel_wmi_thunderbolt ledtrig_audio firmware_attributes_class usbhid
> dell_wmi_descriptor ecdh_generic wmi_bmof videobuf2_common ttm dcdbas
> Mar 28 18:13:53 shilka kernel: snd_timer vfat ucsi_acpi crypto_simd
> processor_thermal_rapl crc16 mc fat dell_smm_hwmon cfg80211 cryptd rapl
> typec_ucsi spi_nor intel_cstate i2c_hid_acpi mei_me drm_display
> │ _helper i2c_i801 typec snd intel_rapl_common int3403_thermal
> intel_uncore soundcore psmouse rfkill pcspkr thunderbolt mtd i2c_smbus
> i2c_hid
> video intel_lpss_pci int340x_thermal_zone intel_soc_dts_iosf int
> │ el_pch_thermal roles cec intel_lpss mei intel_hid idma64 intel_gtt
> sparse_keymap acpi_tad wmi int3400_thermal acpi_thermal_rel acpi_pad mac_hid
> vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) pkcs8_key_parser c
> │ rypto_user fuse dm_mod loop bpf_preload ip_tables x_tables
> rtsx_pci_sdmmc serio_raw atkbd mmc_core nvme libps2 vivaldi_fmap nvme_core
> spi_intel_pci xhci_pci nvme_common i8042 spi_intel rtsx_pci xhci_pci_r
> │ enesas serio f2fs crc32_generic crc32_pclmul lz4hc_compress
> 40 │ Mar 28 18:13:53 shilka kernel: CR2: 0000000000000000
> 41 │ Mar 28 18:13:53 shilka kernel: ---[ end trace 0000000000000000 ]---
> 42 │ Mar 28 18:13:53 shilka kernel: RIP:
> 0010:__replace_atomic_write_block+0x184/0x620 [f2fs]
> 43 │ Mar 28 18:13:53 shilka kernel: Code: 74 0b 48 3b 5c 24 38 0f 85 29
> 01
> 00 00 48 8b 04 24 48 8b 95 80 03 00 00 48 c7 44 24 38 00 00 00 00 48 c7 44 24
> 30 00 00 00 00 <44> 8b 00 66 90 48 8b 44 24 58 65 48 2b
> │ 04 25 28 00 00 00 0f 85 7c
> 44 │ Mar 28 18:13:53 shilka kernel: RSP: 0018:ffffb4a246817c80 EFLAGS:
> 00010246
> 45 │ Mar 28 18:13:53 shilka kernel: RAX: 0000000000000000 RBX:
> ffffee060710d500 RCX: 0000000000ec8c06
> 46 │ Mar 28 18:13:53 shilka kernel: RDX: ffff963c72a217e8 RSI:
> 0000000000000001 RDI: ffffee060710d500
> 47 │ Mar 28 18:13:53 shilka kernel: RBP: ffff963ab0333960 R08:
> ffff963aebe108a0 R09: 0000000080380011
> 48 │ Mar 28 18:13:53 shilka kernel: R10: 0000000000000088 R11:
> ffffffffffffffff R12: 0000000000000000
> 49 │ Mar 28 18:13:53 shilka kernel: R13: 00000000010ea75c R14:
> 0000000000000000 R15: ffff963a412e3000
> 50 │ Mar 28 18:13:53 shilka kernel: FS: 00007f68dff0a6c0(0000)
> GS:ffff963dbe780000(0000) knlGS:0000000000000000
> 51 │ Mar 28 18:13:53 shilka kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
> 0000000080050033
> 52 │ Mar 28 18:13:53 shilka kernel: CR2: 0000000000000000 CR3:
> 0000000378db8001 CR4: 00000000003706e0
> 53 │ Mar 28 18:13:53 shilka kernel: note: ThreadPoolForeg[82195] exited
> with irqs disabled
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You are watching the assignee of the bug.
>
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2023-03-29 17:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 7:01 [f2fs-dev] [Bug 217266] New: kernel panic on f2fs filesystem when f2fs_commit_atomic_write bugzilla-daemon
2023-03-29 17:58 ` bugzilla-daemon [this message]
2023-03-30 2:48 ` [f2fs-dev] [Bug 217266] " bugzilla-daemon
2023-03-30 3:31 ` Chao Yu
2023-03-30 7:35 ` Micha L via Linux-f2fs-devel
2023-03-30 3:31 ` bugzilla-daemon
2023-03-30 7:35 ` bugzilla-daemon
2023-04-03 14:07 ` bugzilla-daemon
2023-04-03 16:59 ` bugzilla-daemon
2023-04-03 17:37 ` Micha L via Linux-f2fs-devel
2023-04-03 17:37 ` 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-217266-202145-g69mVLk97s@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).