diff options
| author | Dmitry Vyukov <dvyukov@google.com> | 2020-07-13 16:55:16 +0200 |
|---|---|---|
| committer | Dmitry Vyukov <dvyukov@google.com> | 2020-07-14 23:21:01 +0200 |
| commit | 1efec8f5c790ea668e8ad4c72e9b7194d093fdfe (patch) | |
| tree | bd69310bfddacfc41f16144efaef365fdb5f1ac6 /sys/linux | |
| parent | 609fb51750f5938bd47f9b78c3d7d8fb435d069c (diff) | |
dashboard/app: say "issue" instead of "crash"
We've got several complains re using of word "crash" in all syzbot reports, e.g.:
https://groups.google.com/d/msg/syzkaller-bugs/8rFLFgQR9fo/HBYUXIRyBAAJ
https://groups.google.com/d/msg/syzkaller-bugs/3nlcT8Wn7hg/8Th16X3DBAAJ
Another suggested that "crash" is too hard for e.g. a LOCKDEP splat:
https://groups.google.com/d/msg/syzkaller/YzHLAU0dXpI/WOqq1ggBBQAJ
Another terminology complaint was regarding the following fact.
When we test a patch, we only detect if it still triggers _any_ issue
(not necessary the original one). Currently we way "still triggers crash"
(without any article, which is probably wrong from English perspective
anyway). We did not say "the", but people assumed that and complained.
Explicitly say "a".
Also replace all uses of "bug" with "issue" for consistency.
And use "final oops" instead of "final crash", which seems
to be standard terminology at least for Linux:
https://en.wikipedia.org/wiki/Linux_kernel_oops
Diffstat (limited to 'sys/linux')
0 files changed, 0 insertions, 0 deletions
