Still solvable in userspace except for static binaries. There's no reason
the library which you LD_PRELOAD can't delete/invalidate the LD_PRELOAD
variable in the environment for example, or use an environment variable to
indicate something like CHILD_HACK_DEPTH=1 before initial running and then
the library can decrement this and if it is zero, stop doing the hack. Or
any number of other solutions, all which happily live in userland.
Still, the module is useful for static binaries and convenience.
Just don't underestimate what you can do in userland if you try.
David.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu