SUSFS LKM Loader

How the loader works

• A probe before and after loading. bin/susfs_probe asks the kernel, through the susfs supercall, whether a SUSFS interface already answers. If one does, it leaves it alone. If the answer is unclear, it refuses to load. After loading it checks again. The probe's C source ships in the zip.
• Strict kernel matching. A release only matches in the canonical GKI form, version then a numeric patch level then the Android tag. Reordered or odd strings such as 6.6.118-vendor-android15-8 are refused, because the upstream loader may patch vermagic and a wrong pick could look like a successful load.
• Standard boot stage. It loads at the normal module post-fs-data stage, writes its log to load.log, and installs no common boot scripts, init RC or sepolicy changes.
• Source included. The full pinned upstream source archive and the license travel in the zip.

Kernels it covers

arm64 only, eight KMIs: android12-5.10, android13-5.10, android13-5.15, android14-5.15, android14-6.1, android15-6.6, android16-6.12 and android17-6.18. These are kernel branches, not Android versions. Non-GKI kernels are unsupported, and vendor ABI differences can still stop a listed KMI from loading.

The author has on-device loading evidence only for android15-6.6. Selection for the other seven is tested on a PC, not on phones.

Install, check, remove

1. Install the zip in a KernelSU-compatible manager. The installer refuses Magisk and non-arm64 devices, and loads nothing during installation.
2. Reboot manually to activate it.
3. Check /data/adb/modules/susfs_lkm_loader/load.log, not lsmod.
4. To remove it, disable or uninstall it in the module list and reboot. It never runs rmmod on a live system, and deleting the .ko doesn't unload a running module.