News for hackers. Stuff that matters.
Re:Linux Kernel Rust Code Sees Its First CVE Vulnerability by woodruffw on Wednesday December 17, 2025 @02:14PM (#46304130)
I think unsafe Rust is harder to write than C. However, that's because unsafe Rust makes you think about the invariants that you'd need to preserve in a correct C program, so it's no harder to write than correct C.

In other words: unsafe Rust is harder, but only in an apples-and-oranges sense. If you compare it to the same diligence you'd need to exercise in writing safer C, it would be about the same.

Re:Linux Kernel Rust Code Sees Its First CVE Vulnerability by jackrabbit1997 on Wednesday December 17, 2025 @02:24PM (#46304265)
How would you describe the aliasing requirements of C and Rust, and do you consider them the same, as well as equally difficult?
Re:Linux Kernel Rust Code Sees Its First CVE Vulnerability by woodruffw on Wednesday December 17, 2025 @02:30PM (#46304343)
Safe Rust has more strict aliasing requirements than C, so to write sound unsafe Rust that interoperates with safe Rust you need to do more work than the equivalent C code would involve. But per above, this is the apples-and-oranges comparison: the equivalent C code will compile, but is statistically more likely to be incorrect. Moreover, it's going to be incorrect in a way that isn't localizable.
Re:Linux Kernel Rust Code Sees Its First CVE Vulnerability by jackrabbit1997 on Wednesday December 17, 2025 @08:57PM (#46308109)
Are you using an LLM to write your posts?
Re:Linux Kernel Rust Code Sees Its First CVE Vulnerability by woodruffw on Wednesday December 17, 2025 @09:20PM (#46308257)
No, that’s just how I write. Do you normally insinuate from green accounts?