The critical thing to understand is namespaces are visibility walls, not security boundaries. They prevent a process from seeing things outside its namespace. They do not prevent a process from exploiting the kernel that implements the namespace. The process still makes syscalls to the same host kernel. If there is a bug in the kernel’s handling of any syscall, the namespace boundary does not help.
writevSync(batch) { for (const c of batch) addChunk(c); return true; },
，这一点在快连下载-Letsvpn下载中也有详细论述
union alloc_header{
Foundational to this approach is the need to cross from the Unreal C++ boundary into the C# DLL code. This boundary is inherently risky as it lacks much of the standard safety checks we normally rely on in managed code.