[issue]: VTOY_LINUX_REMOUNT doesn't work on the latest Kali (LinuxKernel6.5,dm_patch issue)

[qqzwc]

Official FAQ

• I have checked the official FAQ.

Ventoy Version

1.0.96

What about latest release

Yes. I have tried the latest release, but the bug still exist.

Try alternative boot mode

Yes. I have tried them, but the bug still exist.

BIOS Mode

UEFI Mode

Partition Style

MBR

Disk Capacity

1TB

Disk Manufacturer

Netac

Image file checksum (if applicable)

Yes.

Image file download link (if applicable)

https://cdimage.kali.org/kali-2023.4/kali-linux-2023.4-live-amd64.iso

What happened?

normal boot mode:VTOY_LINUX_REMOUNT doesn't work
Error mounting /dev/sda1 at /media/kali/Ventoy:/dev/sda1 already mountded or mount point busy

grub2 boot mode:cann't boot,stuck at kali boot logo

PC:Redmi Book 14 2022 (i5-12500H),FlashDisk: Netac ZSlim (mSATA SSD 1TB MBR exFAT)

It works fine on Kali with Kernel 6.1 (kali-linux-2023.1-live-amd64.iso , kali-linux-2023-W11-live-amd64.iso),but doesn't work on Kali with Kernel 6.5 (kali-linux-2023.4-live-amd64.iso , kali-linux-2023-W50-live-amd64.iso)

Addtional feedback:It seems that kali can only boot correctly with normal boot method. If you choose grub2 boot method,there will be a flash tip that say (error:file /grub/unicode.pf2 not found.),after that it will show iso internal boot menu rightly,but it will stuck on kali boot logo.

┌──(kali㉿kali)-[~]
└─$ uname -r
6.5.0-kali3-amd64

┌──(kali㉿kali)-[~]
└─$ cat /proc/version
Linux version 6.5.0-kali3-amd64 (devel@kali.org) (gcc-13 (Debian 13.2.0-4) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC Debian 6.5.6-1kali1 (2023-10-09)

┌──(kali㉿kali)-[~]
└─$ cat /proc/cmdline
BOOT_IMAGE=/live/vmlinuz-6.5.0-kali3-amd64 boot=live components quiet splash noeject findiso=

┌──(kali㉿kali)-[~]
└─$ dmesg -l err
[ 0.816059] integrity: Problem loading X.509 certificate -65
[ 4.938754] module dm_patch_ibt: .gnu.linkonce.this_module section size must match the kernel's built struct module size at run time
[ 14.499306] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
[ 14.511911] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
[ 14.575265] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
[ 14.591302] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
[ 2395.748257] module dm_patch: .gnu.linkonce.this_module section size must match the kernel's built struct module size at run time

┌──(kali㉿kali)-[~/vtoyboot-1.0.30/tools]
└─$ modinfo ./dm_patch_64.ko
filename: /home/kali/vtoyboot-1.0.30/tools/./dm_patch_64.ko
license: GPL
author: longpanda admin@ventoy.net
description: dmpatch driver
depends:
retpoline: Y
intree: Y
name: dm_patch
vermagic: 5.15.126-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx SMP mod_unload modversions

┌──(kali㉿kali)-[~/vtoyboot-1.0.30/tools]
└─$ sudo insmod ./dm_patch_64.ko
insmod: ERROR: could not insert module ./dm_patch_64.ko: Invalid module format

See related Linux kernel change here:
[PATCH 0/5] module: ELF validation enhancement and cleanups

• /*
• • The ".gnu.linkonce.this_module" ELF section is special. It is
• • what modpost uses to refer to __this_module and let's use rely
• • on THIS_MODULE to point to &__this_module properly. The kernel's
• • modpost declares it on each modules's *.mod.c file. If the struct
• • module of the kernel changes a full kernel rebuild is required.
• • We have a few expectaions for this special section, the following
• • code validates all this for us:
• • o Only one section must exist
• • o We expect the kernel to always have to allocate it: SHF_ALLOC
• • o The section size must match the kernel's run time's struct module

• • size
    

• */
  https://lore.kernel.org/lkml/20230319213542.1790479-1-mcgrof@kernel.org/

https://lore.kernel.org/lkml/20231118025748.2778044-3-mmaurer@google.com/

[youk]

The same issue – #2661