pkg/report: revert bucketing MAX_STACK_TRACE_ENTRIES reports (#1357)

MAX_STACK_TRACE_ENTRIES crash reports caused by a particular issues can come
from any part of the kernel, so bucketing them based on the stack trace is
pointless and only creates duplicate bug reports.
This commit is contained in:
Andrey Konovalov 2019-08-22 14:42:17 +02:00 committed by GitHub
parent 984250d508
commit 0ab81da2cf
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 2 additions and 7 deletions

View File

@ -966,11 +966,6 @@ var linuxOopses = []*oops{
},
},
},
{
title: compile("BUG: MAX_STACK_TRACE_ENTRIES too low!"),
fmt: "BUG: MAX_STACK_TRACE_ENTRIES too low in %[1]v",
stack: warningStackFmt("save_trace", "mark_lock"),
},
{
title: compile("BUG: using __this_cpu_([a-z_]+)\\(\\) in preemptible"),
fmt: "BUG: using __this_cpu_%[1]v() in preemptible code in %[2]v",

View File

@ -1,4 +1,4 @@
TITLE: BUG: MAX_STACK_TRACE_ENTRIES too low in ucma_close
TITLE: BUG: MAX_STACK_TRACE_ENTRIES too low!
[ 185.416858][ T809] BUG: MAX_STACK_TRACE_ENTRIES too low!
[ 185.422408][ T809] turning off the locking correctness validator.

View File

@ -1,4 +1,4 @@
TITLE: BUG: MAX_STACK_TRACE_ENTRIES too low in scsi_remove_host
TITLE: BUG: MAX_STACK_TRACE_ENTRIES too low!
[ 3167.402179][T32668] BUG: MAX_STACK_TRACE_ENTRIES too low!
[ 3167.407738][T32668] turning off the locking correctness validator.