News for hackers. Stuff that matters.
Re:Towards Linux Kernel Memory Safety by pjmlp on Thursday November 16, 2017 @02:44AM (#15710847)
Only works if 100% of the code is available, thus not usable by companies selling commercial libraries.
Re:Towards Linux Kernel Memory Safety by jcelerier on Thursday November 16, 2017 @05:31AM (#15711583)
That's not really relevant when talking about the linux kernel, though, is it ? There's tons and tons of open-source code that could just run clang-analyze today and eliminate swathes of memory bugs.
Re:Towards Linux Kernel Memory Safety by pjmlp on Thursday November 16, 2017 @10:56AM (#15713668)
Sure it is, starting by the GPU drivers.
Re:Towards Linux Kernel Memory Safety by fpoling on Thursday November 16, 2017 @03:18AM (#15710978)
Static checker can work in principle on binary code. Alternatively, one can annotate API the library provides for the static checker. This is especially feasible with C where API types and usage is typically rather simple. Clearly, this implies trusting API to be implemented correctly or at least using the static checker to prove that memory-safety bugs are originated in the library, not in the application code.