3510203fa6
This idea is borrowed from simonpunk's susfs4ksu. What we see here is that, yeah well, lets just have userspace send us what it wants unmounted, this is better than hardcoding everything. This also solves that issue where MNT_DETACH fails, as long as we send unmountables in proper order. A small anti-duplicate mechanism is also added. While in-kernel umount is a bit worse than zygisk-provider-based ones, this can still serve as a healthy alternative. --------- Signed-off-by: backslashxx <118538522+backslashxx@users.noreply.github.com> Co-authored-by: weishu <twsxtd@gmail.com> Signed-off-by: fc5b87cf <rissu.ntk@gmail.com>
24 lines
513 B
C
24 lines
513 B
C
#ifndef __KSU_H_KERNEL_UMOUNT
|
|
#define __KSU_H_KERNEL_UMOUNT
|
|
|
|
#include <linux/types.h>
|
|
#include <linux/list.h>
|
|
#include <linux/rwsem.h>
|
|
|
|
void ksu_kernel_umount_init(void);
|
|
void ksu_kernel_umount_exit(void);
|
|
|
|
// Handler function to be called from setresuid hook
|
|
int ksu_handle_umount(uid_t old_uid, uid_t new_uid);
|
|
|
|
// for the umount list
|
|
struct mount_entry {
|
|
char *umountable;
|
|
unsigned int flags;
|
|
struct list_head list;
|
|
};
|
|
extern struct list_head mount_list;
|
|
extern struct rw_semaphore mount_list_lock;
|
|
|
|
#endif
|