diff options
Diffstat (limited to 'open_issues/locking.mdwn')
| -rw-r--r-- | open_issues/locking.mdwn | 25 |
1 files changed, 6 insertions, 19 deletions
diff --git a/open_issues/locking.mdwn b/open_issues/locking.mdwn index 1717133a..11a10524 100644 --- a/open_issues/locking.mdwn +++ b/open_issues/locking.mdwn @@ -28,26 +28,13 @@ runtime. Or implementing a [[unit testing]] framework that explicitly checks locking in various code paths. (The latter could serve as a template for implementing unit tests in other parts of the Hurd codebase...) -(A systematic code review would probably suffice to find the existing locking +(A [[systematic code review|security]] would probably suffice to find the +existing locking issues; but it wouldn't document the work in terms of actual code produced, and thus it's not suitable for a GSoC project...) -This task requires experience with debugging locking issues in multithreaded -applications. +This task requires experience with debugging locking issues in +[[multithreaded|multithreading]] applications. -Tools have been written for static code analysis, than can help to locate -and fix such errors. - - * Coccinelle - - * <http://lwn.net/Articles/315686/> - - * <http://www.google.com/search?q=coccinelle+analysis> - - * clang - - * <http://www.google.com/search?q=clang+analysis> - - * Linux' sparse - - * <https://sparse.wiki.kernel.org/> +Tools have been written for automated [[code analysis]]; these can help to +locate and fix such errors. |