Coverity detects these, Clang ThreadSafetyAnalysis too. But tools are smaller part of solution. Integration into process is more important. But again kernel doesn't have real notion of changes, no infra to run analysis, no way to make anybody use it, no way to block submit, etc..
-
-
Show this thread
-
That is no way to make it part of process and scale it. That would not just immediately prevent the bug, but prevent the whole class of bugs in all 20 MLOC with guarantees, cheaply and scalably. But that can't be bolted onto the project on the side, by few volunteers...
Show this thread -
Absence of context (no expand btn) in changes only exacerbates the problem. If you look at actual proposed change https://patchwork.kernel.org/patch/11256477/ No mention of rcu, so why would reviewer even start thinking about the potential problem? There are known solutions to this problem as well...
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.