diff options
| author | Dmitry Vyukov <dvyukov@google.com> | 2017-12-12 11:58:52 +0100 |
|---|---|---|
| committer | Dmitry Vyukov <dvyukov@google.com> | 2017-12-12 11:59:13 +0100 |
| commit | 9d0132a2fb379f6464ea0c08c98e77d361eb564d (patch) | |
| tree | 3f13f6db2a231d84a01286f36a524a7f67da1de0 /pkg/report/testdata/linux/guilty/17 | |
| parent | 1556ebc4cc58b700a076d20ea645dae8c081f1bb (diff) | |
pkg/report: move guilty file test data to testdir/
linux_test.go is total mess and very hard to work with.
Turns out we had 2 tests that do exactly the same
(verify Report), but nobody ever noticed.
Move all test data to testdir/. One file per crash.
Diffstat (limited to 'pkg/report/testdata/linux/guilty/17')
| -rw-r--r-- | pkg/report/testdata/linux/guilty/17 | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/pkg/report/testdata/linux/guilty/17 b/pkg/report/testdata/linux/guilty/17 new file mode 100644 index 000000000..47bd74d30 --- /dev/null +++ b/pkg/report/testdata/linux/guilty/17 @@ -0,0 +1,17 @@ +FILE: net/netfilter/x_tables.c + +=============================== +[ INFO: suspicious RCU usage. ] +Call Trace: + [<ffffffff81c8f6cd>] __dump_stack lib/dump_stack.c:15 [inline] + [<ffffffff81c8f6cd>] dump_stack+0xc1/0x124 lib/dump_stack.c:51 + [<ffffffff81614578>] warn_alloc+0x208/0x230 mm/page_alloc.c:2850 + [<ffffffff816d0915>] __vmalloc_area_node_memcg mm/vmalloc.c:1647 [inline] + [<ffffffff816d0915>] __vmalloc_node_range_memcg+0x375/0x670 mm/vmalloc.c:1690 + [<ffffffff816d0c79>] __vmalloc_node_memcg mm/vmalloc.c:1751 [inline] + [<ffffffff816d0c79>] __vmalloc_node_memcg_flags mm/vmalloc.c:1788 [inline] + [<ffffffff816d0c79>] vmalloc+0x69/0x70 mm/vmalloc.c:1803 + [<ffffffff8279a0b0>] xt_alloc_table_info+0xd0/0x100 net/netfilter/x_tables.c:952 + [<ffffffff829a50bc>] do_replace net/ipv4/netfilter/ip_tables.c:1140 [inline] + [<ffffffff829a50bc>] do_ipt_set_ctl+0x21c/0x430 net/ipv4/netfilter/ip_tables.c:1687 + [<ffffffff827436ac>] nf_sockopt net/netfilter/nf_sockopt.c:105 [inline] |