aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDmitry Vyukov <dvyukov@google.com>2016-09-04 12:31:49 +0200
committerGitHub <noreply@github.com>2016-09-04 12:31:49 +0200
commit80394dfdd551d85fa3fcb1cb5381933b04cce39c (patch)
treef4d144c7296a351b3d27f0151d2f55d403706ea5
parentfcf6db1996e38b9f22768b09a7a69c84383e483d (diff)
Update README.md
-rw-r--r--README.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/README.md b/README.md
index 69572b155..c96c15382 100644
--- a/README.md
+++ b/README.md
@@ -193,6 +193,12 @@ Here are some things to check if there are problems running syzkaller.
In this case, running the `syz-execprog` test with the `-nobody=0` option fixes the problem,
so the main configuration needs to be updated to set `dropprivs` to `false`.
+## External Articles
+
+ - [Coverage-guided kernel fuzzing with syzkaller][https://lwn.net/Articles/677764/] (by David Drysdale)
+ - [ubsan, kasan, syzkaller und co](http://www.strlen.de/talks/debug-w-syzkaller.pdf) [video](https://www.youtube.com/watch?v=Acp0A9X1254) (by Florian Westphal)
+ - [Debugging a kernel crash found by syzkaller](http://vegardno.blogspot.de/2016/08/sync-debug.html) (by Quentin Casasnovas)
+
## Disclaimer
This is not an official Google product.