3 ms·

read the kernel docs and follow best practices. the code is reviewed by thousands of developers, so chances are what makes in into the kernel tree is pretty goo

• mlindner 5y ago
  Anecdotes from kernel maintainers is that memory unsafe code gets pas reviewers all the time. There was even that ethically questionable study that tried and succeed in getting vulnerabilities inserted into the kernel.
• pizza234 5y ago
  First, I've generalized to memory-safe languages, not necessarily Rust. Second, this is exactly the overconfidence that I find troubling. Vulnerabilities caused by memory unsafety are real, pervasive, and inevitable. A few resources you should look at: - the official reports/post by Mozilla and Microsoft about the percentage of vulnerabilities caused by memory unsafety - the mailing lists with the Linux kernel issues (I don't imply any severity; just the amount) There are many summarized posts for the lazier, and I'm talking about high profile authors (or authors writing on behalf of high profile companies). Here's a semi-random one: https://msrc-blog.microsoft.com/2019/07/18/we-need-a-safer-systems-programming-language https://msrc-blog.microsoft.com/2019/07/18/we-need-a-safer-s...
  • b20000 5y ago
    not everyone using linux making a device cares about vulnerabilities. there is no root password on my device and it is not networked.