Mounts are awesome. Aren't they? Through its usage, we accomplished numerous capabilities in root scenario, by temporarily altering files and folders.
But... its 2026. We found news ways to replace where we used to need mounts, and root detection wasn't left to catch dust — numerous detections for mounts were made since then, some that required kernel help to be fixed, or to be very careful with those mounts.
Since its existence, ReZygisk created a mount from its temporary
module.prop to the original one, so that it could modify it, and if a reboot is made, all changes will be reverted. The biggest problem of all this was that it was a global mount. KernelSU utilizes ksud to list module information, so a mount in the app mount namespace would not work.Until... recently. We had problems regarding module.prop leak due to
installd after a commit trying to simplify its umount. However, to fix that, it involved making 64-bit-only devices have it leak unless umount was turned on for the application.To fix that and all other detections regarding mounts we decided to find a way to remove that mount — but keeping the "erase module status when disabled" behavior was a bit tricky to think without the trouble makers.
That's when we remembered about global scripts: They were always executed, regardless of module state. By leveraging them, we could make it always reset ReZygisk's
module.prop with sed (Thanks Ok for the idea!) and that way, have a clean module.prop when ReZygisk's disabled without numerous traces.https://github.com/PerformanC/ReZygisk/commit/28021b1716174c664e3d48e98a337a89673bb795
Mountless for the win!
From the depths within my heart,
ThePedroo.
Less fun in playing with this doll,
Trying to hide emotions post fall.
Deceive your eyes to remember,
The smiles we had last December.
I love you.
