F FreeBSD Security Guest Today at 1:12 AM #1 Invoking the fsync(2) system call on a named pipe will trigger a NULL pointer dereference in the kernel, causing a system panic. Click to expand... Original article here. Consider this when replying. Continue reading...
Invoking the fsync(2) system call on a named pipe will trigger a NULL pointer dereference in the kernel, causing a system panic. Click to expand... Original article here. Consider this when replying. Continue reading...
