From fab7609913c9787bdb79602ff716f5e0d1598c98 Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Sun, 13 Sep 2020 19:30:55 +0200 Subject: tools/check-whitespace.sh: check for trailing whitespaces File types that we don't format automatically can end up with such basic untidiness as trailing whitespaces. Check for these. Remove all existing precedents. --- docs/syzbot.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/syzbot.md') diff --git a/docs/syzbot.md b/docs/syzbot.md index fbeb0e070..bffd6994b 100644 --- a/docs/syzbot.md +++ b/docs/syzbot.md @@ -176,7 +176,7 @@ Suggestions and patches that improve bisection quality for common cases are `syzbot` supports cause bisection (find the commit that introduces a bug) and fix bisection (find the commit that fixes a bug). -The web UI for a specific kernel +The web UI for a specific kernel (say [upstream linux](https://syzkaller.appspot.com/upstream)) shows the `Bisected` status for all bugs. @@ -227,7 +227,7 @@ the provided crash report on the provided reproducer on a freshly-booted machine, so the reproducer worked for it somehow. Note: if the report contains `userspace arch: i386`, -then the program needs to be built with `-m32` flag. +then the program needs to be built with `-m32` flag. `syzbot` uses GCE VMs for testing, but *usually* it is not important. @@ -405,7 +405,7 @@ ask tree maintainers for priority handling. However, syzbot kernel config always includes `CONFIG_DEBUG_AID_FOR_SYZBOT=y` setting, which is not normally present in kernel. What was used for particularly elusive bugs in the past is temporary merging some additional debugging code into `linux-next` under this config setting -(e.g. more debug checks and/or debug output) and waiting for new crash reports from syzbot. +(e.g. more debug checks and/or debug output) and waiting for new crash reports from syzbot. ## Kernel configs -- cgit mrf-deployment