aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorDmitry Vyukov <dvyukov@google.com>2019-03-21 15:28:50 +0100
committerGitHub <noreply@github.com>2019-03-21 15:28:50 +0100
commitc94a70b7be6b7eb9e5f69ba547fd06f11bd4c5d4 (patch)
tree15ee38cfb0a46546a48673ba910d6aa3a8d06dc4 /docs
parent7c9c9fd24f0a02c137b8f438a48c2d69210bfdd1 (diff)
docs: add custom anchors to headers
Add shorter anchors that does not depend on actual text (subject to change). This allows to generate shorter stable links to docs. Let's see if this syntax works.
Diffstat (limited to 'docs')
-rw-r--r--docs/syzbot.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/syzbot.md b/docs/syzbot.md
index 1169b3be5..3119940f5 100644
--- a/docs/syzbot.md
+++ b/docs/syzbot.md
@@ -7,7 +7,7 @@ bugs. All `syzbot`-reported bugs are also CCed to
[syzkaller-bugs mailing list](https://groups.google.com/forum/#!forum/syzkaller-bugs).
Direct all questions to `syzkaller@googlegroups.com`.
-## Bug status tracking
+## Bug status tracking <div id="status"/>
`syzbot` needs to know when a bug is fixed in order to (1) verify that it is
in fact fixed and (2) be able to report other similarly-looking crashes
@@ -18,7 +18,7 @@ the commit reaches all kernel builds on all tracked branches. Only when the
commit reaches all builds, the bug is considered closed (new similarly-looking
crashes create a new bug).
-## Communication with syzbot
+## Communication with syzbot <div id="communication"/>
If you fix a bug reported by `syzbot`, please add the provided `Reported-by`
tag to the commit (`Reported-and-tested-by` and `Tested-by` tags with the
@@ -82,7 +82,7 @@ to some mailing lists (e.g. netdev, netfilter-devel) will trigger patchwork.
Note: see [below](#kmsan-bugs) for testing `KMSAN` bugs.
-## Bisection
+## Bisection <div id="bisection"/>
`syzbot` bisects bugs with reproducers to find commit that introduced the bug.
`syzbot` starts with the commit on which the bug was discovered, ensures that it