[Bug] 70_ksu_safety patch breaks compilation on KernelSU-Next v33188+ (Syntax & Linker errors)

[u1tr0nex]

Describe the bug
The 70_ksu_safety-kernelsu-next.patch is incompatible with the latest KernelSU-Next architecture (v33188 and newer). Applying the patch alongside SUSFS and ZeroMount causes fatal C-compiler syntax errors and linker failures because the patch blueprint modifies legacy functions that have been refactored or deleted in the newest KSU-Next source.

Environment

• Target: Android 14, Kernel 6.1 (GKI)
• Variant: KernelSU-Next (Latest/v33214+)
• Features: SUSFS, ZeroMount

Specific Errors Encountered

1. Linker Error (Undefined Symbol): The patch forces syscall_event_bridge.c to call a legacy function that KSU-Next deleted.

   ld.lld: error: undefined symbol: ksu_handle_faccessat_sucompat
   >>> referenced by syscall_event_bridge.c:63 (drivers/kernelsu/hook/syscall_event_bridge.c:63)
   
   

2. Compiler Error (Broken Syntax): The patch aggressively removes lines in feature/sucompat.c, breaking the #ifdef architecture and leaving orphaned statements.

drivers/kernelsu/feature/sucompat.c:130:2: error: #else without #if
drivers/kernelsu/feature/sucompat.c:252:2: error: #endif without #if

2. Compiler Error (Implicit Declaration): The patch injects references to sh_user_path(), which KernelSU-Next recently renamed to ksud_user_path().

Steps to Reproduce

Run the CI build targeting android14-6.1.

Select KernelSU-Next as the variant (leaving the commit hash blank to pull the latest source).

Enable SUSFS and ZeroMount.

The patch applies cleanly, but the build fails during C-compilation and linking.

Expected behavior
The 70_ksu_safety patch blueprint needs to be rewritten to align with the new v33188+ architecture, specifically updating the function names in sucompat.c and removing the deprecated ksu_handle_faccessat_sucompat hook.