aboutsummaryrefslogtreecommitdiffstats
path: root/pkg/report/linux.go
diff options
context:
space:
mode:
authorAndrey Konovalov <andreyknvl@google.com>2019-08-22 14:42:17 +0200
committerGitHub <noreply@github.com>2019-08-22 14:42:17 +0200
commit0ab81da2cfd823442c235f2dd1896b51b662b115 (patch)
tree9e37c5759466d98f2256dfa328f5ea8a90fae433 /pkg/report/linux.go
parent984250d5080e0bf455725ff96551e35c3ae59457 (diff)
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.
Diffstat (limited to 'pkg/report/linux.go')
-rw-r--r--pkg/report/linux.go5
1 files changed, 0 insertions, 5 deletions
diff --git a/pkg/report/linux.go b/pkg/report/linux.go
index fa1299c22..23348c95c 100644
--- a/pkg/report/linux.go
+++ b/pkg/report/linux.go
@@ -967,11 +967,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",
stack: &stackFmt{