Bug 2305521 - LVM snapshot removal with f2fs causes a kernel NULL pointer de-referencing
Summary: LVM snapshot removal with f2fs causes a kernel NULL pointer de-referencing
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 40
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-08-17 11:28 UTC by Piergiorgio Sartor
Modified: 2025-05-20 19:27 UTC (History)
15 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-05-20 19:27:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Piergiorgio Sartor 2024-08-17 11:28:29 UTC
1. Please describe the problem:

I've a PC (NUC, basically a laptop without screen, battery, keyboard, ...) with classic secure configuration: LUKS + LVM + f2fs. This was chosen in the hope of keeping the SSD wearout low (the PC runs like a mini / micro server).
Since kernel 6.10.x, doing a backup, using LVM snapshots, causes a kernel NULL pointer de-referencing, possibly in f2fs_discard. This happens when removing the snapshot (creation and usage is fine), which causes discards to be issued to the underlying device.
Reboot is not anymore possible, the PC need to be shut down by power off (which is not nice with the FS, in particular f2fs).

2. What is the Version-Release number of the kernel:

6.10.3 and 6.10.4 official Fedora kernel

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

Kernel up to 6.9.x were fine.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Yes.
As described above: LUKS + LVM + f2fs --> create LVM snapshot --> remove LVM snapshot --> "sync" (this last might not be necessary).

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Do not know. I might consider to check, if really, really, really needed. Because reboot is not possible, I would like to avoid hard power off.

6. Are you running any modules that not shipped with directly Fedora's kernel?:

No.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Aug 17 10:07:27 kernel: ------------[ cut here ]------------
Aug 17 10:07:27 kernel: WARNING: CPU: 2 PID: 969 at fs/f2fs/segment.c:1330 __submit_discard_cmd+0x27d/0x400 [f2fs]
Aug 17 10:07:27 kernel: Modules linked in: rpcrdma rdma_cm iw_cm ib_cm ib_core dimlib 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 nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ip_set ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables qrtr hwmon_vid vfat fat spi_nor mtd x86_pkg_temp_thermal intel_powerclamp coretemp iTCO_wdt mei_hdcp kvm_intel mei_pxp intel_pmc_bxt iTCO_vendor_support ee1004 intel_rapl_msr kvm eeepc_wmi asus_wmi sparse_keymap platform_profile rfkill r8169 intel_cstate wmi_bmof processor_thermal_device_pci_legacy realtek processor_thermal_device spi_intel_pci spi_intel i2c_i801 mei_me i2c_smbus processor_thermal_wt_hint mei processor_thermal_rfim idma64 processor_thermal_rapl intel_rapl_common processor_thermal_wt_req processor_thermal_power_floor
Aug 17 10:07:27 kernel:  processor_thermal_mbox intel_soc_dts_iosf intel_pmc_core int3403_thermal int340x_thermal_zone intel_vsec pmt_telemetry int3400_thermal acpi_pad pmt_class acpi_thermal_rel acpi_tad nfsd auth_rpcgss nfs_acl lockd grace sunrpc fuse loop nfnetlink f2fs crc32_generic lz4hc_compress lz4_compress dm_crypt i915 crct10dif_pclmul crc32_pclmul crc32c_intel polyval_generic ghash_clmulni_intel sha512_ssse3 sdhci_pci cqhci sdhci i2c_algo_bit drm_buddy ttm sha256_ssse3 spi_pxa2xx_platform uas mmc_core drm_display_helper usb_storage sha1_ssse3 dw_dmac cec video pinctrl_jasperlake wmi
Aug 17 10:07:27 kernel: CPU: 2 PID: 969 Comm: f2fs_discard-25 Not tainted 6.10.3-200.fc40.x86_64 #1
Aug 17 10:07:27 kernel: Hardware name: ASUSTeK COMPUTER INC. MINIPC PN41-S1/PN41-S1, BIOS 0405 07/07/2022
Aug 17 10:07:27 kernel: RIP: 0010:__submit_discard_cmd+0x27d/0x400 [f2fs]
Aug 17 10:07:27 kernel: Code: 8b 00 3b 46 10 0f 83 ee 00 00 00 48 c7 44 24 50 00 00 00 00 44 39 6c 24 2c 0f 83 a1 fe ff ff 8b 6c 24 2c 31 d2 e9 9e fe ff ff <0f> 0b 48 8b 44 24 48 f0 80 08 04 e9 e9 fe ff ff 65 8b 15 48 3c 53
Aug 17 10:07:27 kernel: RSP: 0018:ffffbfe1c07dfd30 EFLAGS: 00010246
Aug 17 10:07:27 kernel: RAX: 0000000000000000 RBX: ffff9b28055be018 RCX: 000000001d46ffff
Aug 17 10:07:27 kernel: RDX: 000000001d470000 RSI: 000000001d470000 RDI: ffff9b28004c2580
Aug 17 10:07:27 kernel: RBP: 0000000000000000 R08: ffffbfe1c07dfd80 R09: ffffbfe1c07dfe78
Aug 17 10:07:27 kernel: R10: ffff9b2806401000 R11: ffff9b28004c2580 R12: 00000000055be000
Aug 17 10:07:27 kernel: R13: 0000000000000200 R14: ffff9b28055bc000 R15: ffff9b28101c6d90
Aug 17 10:07:27 kernel: FS:  0000000000000000(0000) GS:ffff9b2b70900000(0000) knlGS:0000000000000000
Aug 17 10:07:27 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 17 10:07:27 kernel: CR2: 00005589f3976000 CR3: 0000000130c4e000 CR4: 0000000000350ef0
Aug 17 10:07:27 kernel: Call Trace:
Aug 17 10:07:27 kernel:  <TASK>
Aug 17 10:07:27 kernel:  ? __submit_discard_cmd+0x27d/0x400 [f2fs]
Aug 17 10:07:27 kernel:  ? __warn.cold+0x8e/0xe8
Aug 17 10:07:27 kernel:  ? __submit_discard_cmd+0x27d/0x400 [f2fs]
Aug 17 10:07:27 kernel:  ? report_bug+0xff/0x140
Aug 17 10:07:27 kernel:  ? handle_bug+0x3c/0x80
Aug 17 10:07:27 kernel:  ? exc_invalid_op+0x17/0x70
Aug 17 10:07:27 kernel:  ? asm_exc_invalid_op+0x1a/0x20
Aug 17 10:07:27 kernel:  ? __submit_discard_cmd+0x27d/0x400 [f2fs]
Aug 17 10:07:27 kernel:  __issue_discard_cmd+0x1ca/0x350 [f2fs]
Aug 17 10:07:27 kernel:  issue_discard_thread+0x191/0x480 [f2fs]
Aug 17 10:07:27 kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Aug 17 10:07:27 kernel:  ? __pfx_issue_discard_thread+0x10/0x10 [f2fs]
Aug 17 10:07:27 kernel:  kthread+0xcf/0x100
Aug 17 10:07:27 kernel:  ? __pfx_kthread+0x10/0x10
Aug 17 10:07:27 kernel:  ret_from_fork+0x31/0x50
Aug 17 10:07:27 kernel:  ? __pfx_kthread+0x10/0x10
Aug 17 10:07:27 kernel:  ret_from_fork_asm+0x1a/0x30
Aug 17 10:07:27 kernel:  </TASK>
Aug 17 10:07:27 kernel: ---[ end trace 0000000000000000 ]---
Aug 17 10:07:27 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000010
Aug 17 10:07:27 kernel: #PF: supervisor write access in kernel mode
Aug 17 10:07:27 kernel: #PF: error_code(0x0002) - not-present page
Aug 17 10:07:27 kernel: PGD 1069f9067 P4D 1069f9067 PUD 0 
Aug 17 10:07:27 kernel: Oops: Oops: 0002 [#1] PREEMPT SMP NOPTI
Aug 17 10:07:27 kernel: CPU: 2 PID: 969 Comm: f2fs_discard-25 Tainted: G        W          6.10.3-200.fc40.x86_64 #1
Aug 17 10:07:27 kernel: Hardware name: ASUSTeK COMPUTER INC. MINIPC PN41-S1/PN41-S1, BIOS 0405 07/07/2022
Aug 17 10:07:27 kernel: RIP: 0010:__submit_discard_cmd+0x203/0x400 [f2fs]
Aug 17 10:07:27 kernel: Code: 89 4c 24 20 e8 ee 2e db ca 84 c0 74 14 48 8b 4c 24 20 4c 89 63 08 49 89 5f 28 49 89 4f 30 4c 89 21 48 8b 7c 24 50 8b 44 24 44 <09> 47 10 4c 89 7f 40 48 c7 47 38 a0 f8 af c0 e8 29 8f d0 ca f0 41
Aug 17 10:07:27 kernel: RSP: 0018:ffffbfe1c07dfd30 EFLAGS: 00010202
Aug 17 10:07:27 kernel: RAX: 0000000000000000 RBX: ffff9b28055be018 RCX: ffff9b28055be018
Aug 17 10:07:27 kernel: RDX: ffff9b28055be018 RSI: ffff9b28055be018 RDI: 0000000000000000
Aug 17 10:07:27 kernel: RBP: 0000000000000000 R08: ffff9b28055be018 R09: ffffbfe1c07dfe78
Aug 17 10:07:27 kernel: R10: ffff9b2806401000 R11: ffff9b28004c2580 R12: ffff9b28101c6db8
Aug 17 10:07:27 kernel: R13: 0000000000000200 R14: ffff9b28055bc000 R15: ffff9b28101c6d90
Aug 17 10:07:27 kernel: FS:  0000000000000000(0000) GS:ffff9b2b70900000(0000) knlGS:0000000000000000
Aug 17 10:07:27 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 17 10:07:27 kernel: CR2: 0000000000000010 CR3: 0000000130c4e000 CR4: 0000000000350ef0
Aug 17 10:07:27 kernel: Call Trace:
Aug 17 10:07:27 kernel:  <TASK>
Aug 17 10:07:27 kernel:  ? __die_body.cold+0x19/0x27
Aug 17 10:07:27 kernel:  ? page_fault_oops+0x15a/0x2f0
Aug 17 10:07:27 kernel:  ? __submit_discard_cmd+0x27d/0x400 [f2fs]
Aug 17 10:07:27 kernel:  ? exc_page_fault+0x7e/0x180
Aug 17 10:07:27 kernel:  ? asm_exc_page_fault+0x26/0x30
Aug 17 10:07:27 kernel:  ? __submit_discard_cmd+0x203/0x400 [f2fs]
Aug 17 10:07:27 kernel:  __issue_discard_cmd+0x1ca/0x350 [f2fs]
Aug 17 10:07:27 kernel:  issue_discard_thread+0x191/0x480 [f2fs]
Aug 17 10:07:27 kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Aug 17 10:07:27 kernel:  ? __pfx_issue_discard_thread+0x10/0x10 [f2fs]
Aug 17 10:07:27 kernel:  kthread+0xcf/0x100
Aug 17 10:07:27 kernel:  ? __pfx_kthread+0x10/0x10
Aug 17 10:07:27 kernel:  ret_from_fork+0x31/0x50
Aug 17 10:07:27 kernel:  ? __pfx_kthread+0x10/0x10
Aug 17 10:07:27 kernel:  ret_from_fork_asm+0x1a/0x30
Aug 17 10:07:27 kernel:  </TASK>
Aug 17 10:07:27 kernel: Modules linked in: rpcrdma rdma_cm iw_cm ib_cm ib_core dimlib 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 nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ip_set ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables qrtr hwmon_vid vfat fat spi_nor mtd x86_pkg_temp_thermal intel_powerclamp coretemp iTCO_wdt mei_hdcp kvm_intel mei_pxp intel_pmc_bxt iTCO_vendor_support ee1004 intel_rapl_msr kvm eeepc_wmi asus_wmi sparse_keymap platform_profile rfkill r8169 intel_cstate wmi_bmof processor_thermal_device_pci_legacy realtek processor_thermal_device spi_intel_pci spi_intel i2c_i801 mei_me i2c_smbus processor_thermal_wt_hint mei processor_thermal_rfim idma64 processor_thermal_rapl intel_rapl_common processor_thermal_wt_req processor_thermal_power_floor
Aug 17 10:07:27 kernel:  processor_thermal_mbox intel_soc_dts_iosf intel_pmc_core int3403_thermal int340x_thermal_zone intel_vsec pmt_telemetry int3400_thermal acpi_pad pmt_class acpi_thermal_rel acpi_tad nfsd auth_rpcgss nfs_acl lockd grace sunrpc fuse loop nfnetlink f2fs crc32_generic lz4hc_compress lz4_compress dm_crypt i915 crct10dif_pclmul crc32_pclmul crc32c_intel polyval_generic ghash_clmulni_intel sha512_ssse3 sdhci_pci cqhci sdhci i2c_algo_bit drm_buddy ttm sha256_ssse3 spi_pxa2xx_platform uas mmc_core drm_display_helper usb_storage sha1_ssse3 dw_dmac cec video pinctrl_jasperlake wmi
Aug 17 10:07:27 kernel: CR2: 0000000000000010
Aug 17 10:07:27 kernel: ---[ end trace 0000000000000000 ]---
Aug 17 10:07:27 kernel: RIP: 0010:__submit_discard_cmd+0x203/0x400 [f2fs]
Aug 17 10:07:27 kernel: Code: 89 4c 24 20 e8 ee 2e db ca 84 c0 74 14 48 8b 4c 24 20 4c 89 63 08 49 89 5f 28 49 89 4f 30 4c 89 21 48 8b 7c 24 50 8b 44 24 44 <09> 47 10 4c 89 7f 40 48 c7 47 38 a0 f8 af c0 e8 29 8f d0 ca f0 41
Aug 17 10:07:27 kernel: RSP: 0018:ffffbfe1c07dfd30 EFLAGS: 00010202
Aug 17 10:07:27 kernel: RAX: 0000000000000000 RBX: ffff9b28055be018 RCX: ffff9b28055be018
Aug 17 10:07:27 kernel: RDX: ffff9b28055be018 RSI: ffff9b28055be018 RDI: 0000000000000000
Aug 17 10:07:27 kernel: RBP: 0000000000000000 R08: ffff9b28055be018 R09: ffffbfe1c07dfe78
Aug 17 10:07:27 kernel: R10: ffff9b2806401000 R11: ffff9b28004c2580 R12: ffff9b28101c6db8
Aug 17 10:07:27 kernel: R13: 0000000000000200 R14: ffff9b28055bc000 R15: ffff9b28101c6d90
Aug 17 10:07:27 kernel: FS:  0000000000000000(0000) GS:ffff9b2b70900000(0000) knlGS:0000000000000000
Aug 17 10:07:27 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 17 10:07:27 kernel: CR2: 0000000000000010 CR3: 0000000130c4e000 CR4: 0000000000350ef0
Aug 17 10:07:27 kernel: note: f2fs_discard-25[969] exited with irqs disabled
Aug 17 10:07:27 kernel: ------------[ cut here ]------------
Aug 17 10:07:27 kernel: WARNING: CPU: 2 PID: 969 at kernel/exit.c:825 do_exit+0x8a9/0xaa0
Aug 17 10:07:27 kernel: Modules linked in: rpcrdma rdma_cm iw_cm ib_cm ib_core dimlib 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 nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ip_set ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables qrtr hwmon_vid vfat fat spi_nor mtd x86_pkg_temp_thermal intel_powerclamp coretemp iTCO_wdt mei_hdcp kvm_intel mei_pxp intel_pmc_bxt iTCO_vendor_support ee1004 intel_rapl_msr kvm eeepc_wmi asus_wmi sparse_keymap platform_profile rfkill r8169 intel_cstate wmi_bmof processor_thermal_device_pci_legacy realtek processor_thermal_device spi_intel_pci spi_intel i2c_i801 mei_me i2c_smbus processor_thermal_wt_hint mei processor_thermal_rfim idma64 processor_thermal_rapl intel_rapl_common processor_thermal_wt_req processor_thermal_power_floor
Aug 17 10:07:27 kernel:  processor_thermal_mbox intel_soc_dts_iosf intel_pmc_core int3403_thermal int340x_thermal_zone intel_vsec pmt_telemetry int3400_thermal acpi_pad pmt_class acpi_thermal_rel acpi_tad nfsd auth_rpcgss nfs_acl lockd grace sunrpc fuse loop nfnetlink f2fs crc32_generic lz4hc_compress lz4_compress dm_crypt i915 crct10dif_pclmul crc32_pclmul crc32c_intel polyval_generic ghash_clmulni_intel sha512_ssse3 sdhci_pci cqhci sdhci i2c_algo_bit drm_buddy ttm sha256_ssse3 spi_pxa2xx_platform uas mmc_core drm_display_helper usb_storage sha1_ssse3 dw_dmac cec video pinctrl_jasperlake wmi
Aug 17 10:07:27 kernel: CPU: 2 PID: 969 Comm: f2fs_discard-25 Tainted: G      D W          6.10.3-200.fc40.x86_64 #1
Aug 17 10:07:27 kernel: Hardware name: ASUSTeK COMPUTER INC. MINIPC PN41-S1/PN41-S1, BIOS 0405 07/07/2022
Aug 17 10:07:27 kernel: RIP: 0010:do_exit+0x8a9/0xaa0
Aug 17 10:07:27 kernel: Code: f6 e8 2b e1 ff ff e9 9b fd ff ff 4c 89 e6 bf 05 06 00 00 e8 09 19 01 00 e9 71 f8 ff ff 48 89 df e8 3c c5 13 00 e9 55 f9 ff ff <0f> 0b e9 cb f7 ff ff 0f 0b e9 88 f7 ff ff 4c 89 e6 48 89 df e8 de
Aug 17 10:07:27 kernel: RSP: 0018:ffffbfe1c07dfed8 EFLAGS: 00010286
Aug 17 10:07:27 kernel: RAX: 0000000400000000 RBX: ffff9b280647a7c0 RCX: 0000000000000000
Aug 17 10:07:27 kernel: RDX: 0000000000000001 RSI: 0000000000002710 RDI: ffff9b2800eb7380
Aug 17 10:07:27 kernel: RBP: ffff9b2800ebb180 R08: 0000000000000000 R09: 645f73663266203a
Aug 17 10:07:27 kernel: R10: 0000000000000064 R11: 3266203a65746f6e R12: 0000000000000009
Aug 17 10:07:27 kernel: R13: ffff9b2800eb7380 R14: 0000000000000000 R15: 0000000000000000
Aug 17 10:07:27 kernel: FS:  0000000000000000(0000) GS:ffff9b2b70900000(0000) knlGS:0000000000000000
Aug 17 10:07:27 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 17 10:07:27 kernel: CR2: 0000000000000010 CR3: 0000000130c4e000 CR4: 0000000000350ef0
Aug 17 10:07:27 kernel: Call Trace:
Aug 17 10:07:27 kernel:  <TASK>
Aug 17 10:07:27 kernel:  ? do_exit+0x8a9/0xaa0
Aug 17 10:07:27 kernel:  ? __warn.cold+0x8e/0xe8
Aug 17 10:07:27 kernel:  ? do_exit+0x8a9/0xaa0
Aug 17 10:07:27 kernel:  ? report_bug+0xff/0x140
Aug 17 10:07:27 kernel:  ? handle_bug+0x3c/0x80
Aug 17 10:07:27 kernel:  ? exc_invalid_op+0x17/0x70
Aug 17 10:07:27 kernel:  ? asm_exc_invalid_op+0x1a/0x20
Aug 17 10:07:27 kernel:  ? do_exit+0x8a9/0xaa0
Aug 17 10:07:27 kernel:  ? do_exit+0x6d/0xaa0
Aug 17 10:07:27 kernel:  make_task_dead+0x90/0x90
Aug 17 10:07:27 kernel:  rewind_stack_and_make_dead+0x16/0x20
Aug 17 10:07:27 kernel: RIP: 0000:0x0
Aug 17 10:07:27 kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
Aug 17 10:07:27 kernel: RSP: 0000:0000000000000000 EFLAGS: 00000000 ORIG_RAX: 0000000000000000
Aug 17 10:07:27 kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
Aug 17 10:07:27 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Aug 17 10:07:27 kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
Aug 17 10:07:27 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Aug 17 10:07:27 kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Aug 17 10:07:27 kernel:  </TASK>
Aug 17 10:07:27 kernel: ---[ end trace 0000000000000000 ]---



Reproducible: Always

Comment 1 Piergiorgio Sartor 2024-10-19 18:03:57 UTC
Not solved with kernel 6.11.3 having the exact same issue.
Checking the kernel updates about f2fs it seems that there is some rework for zoned devices, which includes "discard" or "trim" operations.
Any idea if any of those could be the culprit?

Thanks,

pg

Comment 2 Piergiorgio Sartor 2024-10-26 18:56:02 UTC
I tried to investigate a bit this item.
On a different PC, I could not reproduce the problem.
On this PC, I notice the issue occurred immediately when creating the snapshot, not when removing it.
This PC has 3 LV:

root (32GiB)
home (480GiB)
data (256GiB)

The one causing the problem was "home".
So I tried the other two, and everything was working fine, no issue.
The only difference I could see is the size.

After, I re-tried "home", and, surprise, no problem also there.

It seems something fishy is happening.
From one side, it's good the problem is gone, from the other... It's not solved..

Hope this helps,

pg

Comment 3 Piergiorgio Sartor 2024-10-26 19:21:37 UTC
One more update.
After reboot, problem again there.
And again reboot, if I snapshot another LV, I can, after, snapshot "home" without problems.
If I snapshot "home" first, then there is the NULL pointer de-referencing error.

Not sure what to do with this, but I would be nice if someone could provide some hints...

Thanks,

pg

Comment 4 Piergiorgio Sartor 2024-12-12 18:59:22 UTC
Hi all,

kernel-6.12.4-100.fc40.x86_64.rpm (from Koji build) seems to carry the patch for this problem.
Some testing resulted in no issues anymore.

I think you can close the bug.

Thanks!

Merry Christmas & Happy New Year!

bye,

pg

Comment 5 Piergiorgio Sartor 2025-04-27 14:24:44 UTC
I think this was fixed and can be closed.
Thanks!

Comment 6 Aoife Moloney 2025-04-28 13:40:05 UTC
This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '40'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 40 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 7 Piergiorgio Sartor 2025-05-17 14:56:55 UTC
Hi all, as already reported, this was fixed.
Can be closed (even if it will automatically).

Comment 8 Aoife Moloney 2025-05-20 19:27:36 UTC
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.