aboutsummaryrefslogtreecommitdiffstats
path: root/pkg/report/testdata
Commit message (Collapse)AuthorAgeFilesLines
...
* pkg/report: ignore warn_bogus_irq_restore frameDmitry Vyukov2021-03-051-0/+43
|
* pkg/report: improve witness reports on OpenBSD (#2468)Anton Lindqvist2021-03-041-0/+287
| | | | | | | | | The witness output was recently changed in order to aid tracking down scenarios in which lock ordering data is missing. This is probably a bug and turning them into unique reports should hopefully help syzkaller being able to find a reproducer. The existing inode suppression must be tweaked a bit order to not flag the relevant reports as suppressed.
* pkg/report: added extra ignore cases for androidDarby Sauter2021-02-261-0/+11
| | | | | Ignore cases that match "INFO:" that were not important. These occured on Pixel3XL running Android 11.
* pkg/report: add another arm64 reportDmitry Vyukov2021-02-251-0/+63
| | | | | Extracted from: https://groups.google.com/g/syzkaller/c/cXw5z215P5E/m/jBvwJ3IsAQAJ
* pkg/report: ignore another android panic in logDmitry Vyukov2021-02-251-0/+4
|
* pkg/report: ignore kcsan_setup_watchpoint in reportsMarco Elver2021-02-221-0/+96
| | | | | | | | kcsan_setup_watchpoint() reads the value before and after the delay to check for value changes. If the memory location is inaccessible, do not report the bug in kcsan_setup_watchpoint() but instead in the caller. This also allows properly deduplicating related reports from non-KCSAN configs.
* pkg/report: detect executor failuresDmitry Vyukov2021-02-211-0/+26
| | | | | | | | | | | | Currently all executor fail errors go into "lost connection" bucket. This is not very useful. First, there are different executor failures. Second, it's not possible to understand what failures happen how frequently. Third, there are not authentic lost connection. Create separate SYZFAIL: bugs for them. Update #573 Update #502 Update #318
* pkg/report: fix NUM replacementDmitry Vyukov2021-02-121-0/+45
|
* pkg/report: ignore krealloc in KFENCE reportsDmitry Vyukov2021-02-041-0/+26
|
* pkg/report: support parsing KFENCE reportsDmitry Vyukov2021-02-0211-0/+389
|
* pkg/report: ignore __seqprop_assertDmitry Vyukov2021-01-271-0/+93
|
* pkg/report: merge task hung and task can't die reportsDmitry Vyukov2021-01-2745-0/+45
| | | | | | | Both these passive hangs sometimes happen due to the same underlying issue. Merge them together. Update #1575
* pkg/report: merge rcu stalls and soft lockupsDmitry Vyukov2021-01-2787-4/+87
| | | | | | | Both these active stalls sometimes happen due to the same underlying issue. Merge them together. Update #1575
* pkg/report: merge KMSAN bugs into KASAN bugsDmitry Vyukov2021-01-2712-0/+12
| | | | Update #1575
* pkg/report: ignore kthread more precisely in stall reportsDmitry Vyukov2021-01-221-0/+50
|
* pkg/report: merge KASAN/GPF/etc crashes togetherDmitry Vyukov2021-01-22140-1/+140
| | | | | | | These cause lots of duplicates. See existing syzbot bugs and the issue. Update #1575
* pkg/report: add alt title for "kernel BUG" oopsDmitry Vyukov2021-01-1718-23/+36
| | | | Update #1575
* pkg/report: add more "kernel BUG at" oops samplesDmitry Vyukov2021-01-1712-0/+629
| | | | Update #1575
* pkg/report: skip all kmalloc/kcalloc framesDmitry Vyukov2021-01-173-2/+79
| | | | | | | | | Initially I tried to skip kmalloc frames more carefully to report proper test names in KASAN tests (338, 340). But as the result we badly parsed a real report, while nobody cares much about how we parse KASAN tests that happen to contain "kmalloc" in test function name. Skip all kmalloc frames now.
* pkg/report: ignore mem/strdup functionsDmitry Vyukov2021-01-141-0/+77
|
* pkg/report: add more mte report samplesDmitry Vyukov2021-01-135-0/+486
|
* pkg/report: parse KASAN_HW_TAGS reportsDmitry Vyukov2021-01-121-0/+78
|
* pkg/report: fix parsing of arm "unable to handle kernel NULL pointer ↵Dmitry Vyukov2021-01-091-0/+106
| | | | dereference"
* pkg/report: add more oops samplesDmitry Vyukov2021-01-055-0/+577
| | | | Some of these were classified as corrupted at some point.
* pkg/report: improve parsing of "HARDIRQ-safe -> HARDIRQ-unsafe lock order ↵Dmitry Vyukov2021-01-055-0/+1601
| | | | detected"
* pkg/report: improve arm oops parsingDmitry Vyukov2020-12-317-68/+122
| | | | | | Stop treating stack memory dump as beginning of stack trace. It's not getting anywhere, we are just getting more and more special cases (see test 555).
* pkg/report: improve arm oops parsingDmitry Vyukov2020-12-301-0/+46
|
* pkg/report: implement arm oops parsingDmitry Vyukov2020-12-3014-9/+675
|
* pkg/report: add more arm64/riscv64 oops examplesDmitry Vyukov2020-12-295-0/+202
|
* pkg/report: add anoter report exampleDmitry Vyukov2020-12-231-0/+65
| | | | Update #1575
* pkg/report: skip mark_lockDmitry Vyukov2020-12-161-0/+42
|
* pkg/report: replace IP addresses in titlesDmitry Vyukov2020-12-081-0/+45
|
* pkg/report: better guilty file extraction with lockdep headerDmitry Vyukov2020-12-071-0/+132
| | | | | | | LOCKDEP can add "hard/softirs last enabled/disabled at" lines with more files at the top. These files are generally not related, or at least out of order. We want to extract the file from stacks, so ignore these lines.
* pkg/report: properly attribute stalls in tasklet'sDmitry Vyukov2020-12-071-0/+185
|
* pkg/report: make panic oops on openbsd more stringent (#2315)Anton Lindqvist2020-12-051-0/+24
| | | | | | | | | | | | | It looks we got a couple of odd crashes where the syz-executor is probably hanging but the VM is still responsive[1]. Does the hypervisor try to diagnose the VM under such circumstances? Since the VM is still responsive, the input written to the console is echoed back which in turns causes a panic to be detected. If this theory is true, we can avoid detecting such false positives by making the oops indicator disjoint from the input written to the console. [1] https://syzkaller.appspot.com/bug?id=af604b59c590384e9faa00dfc958ef87a922ae71
* pkg/report: skip drivers/usb/core/urb.c as guilty fileDmitry Vyukov2020-11-304-0/+247
| | | | | | | | | | | We are getting lots of WARNINGs in urb.c and all of them seem to mean a bug in a particular driver. And fixes for these bugs go into a particular driver code. But we send all of them to urb.c maintainers. Skip urb.c as a guilty file. If a bug happens to be in urb.c for real, a driver maintainers should CC USB core maintainers on it. Update #2284
* pkg/report: handle rwlock debug oopsesDmitry Vyukov2020-11-302-1/+17
|
* pkg/report: arm64 supportDmitry Vyukov2020-10-2822-9/+624
| | | | Add arm64 test crash and some parsing logic fixes/improvements.
* pkg/report: suppress witness vnode lock order reversal on OpenBSDAnton Lindqvist2020-10-272-1/+295
| | | | | | | | | | These reports are not that helpful and are rarely a problem as each vnode has a unique lock. Reports from witness regarding lock order reversal between two vnode locks are already suppressed by the kernel, see RWL_IS_VNODE in the rwlock(9) manual. While here, update `testdata/openbsd/report/10` as this report was generated before I prefixed all output from witness.
* pkg/report: ignore "ddb.onpanic" on netbsdDmitry Vyukov2020-10-261-0/+14
|
* pkg/report: add a test for another type of rcu stall reportDmitry Vyukov2020-10-211-0/+96
|
* pkg/report: support divide_error: crashesDmitry Vyukov2020-10-131-0/+66
|
* pkg/report: fix a testDmitry Vyukov2020-09-231-0/+1
|
* pkg/report: detect hrtimer_run as stall anchor frameDmitry Vyukov2020-09-231-0/+111
|
* pkg/report: support new linux UBSAN formatDmitry Vyukov2020-09-161-0/+36
| | | | Update #1523
* pkg/report: skip rb tree functions in linux reportsDmitry Vyukov2020-09-1310-0/+475
| | | | | | RB tree is just a container (like list we already skip), the bug is usually in the caller. Skip RB frames. The new titles are much more informative and have lower chances of collisions.
* pkg/report: add gvisor "stuck task" patternDmitry Vyukov2020-09-122-0/+133
|
* pkg/report: fix parsing of kernel-usb-infoleakDmitry Vyukov2020-08-111-0/+94
| | | | | | It used to use warningStackFmt, it is wrong, this is not a WARNING. As the result it previously parsed as: KMSAN: kernel-usb-infoleak in __kmalloc
* pkg/report: fix uvm_fault report detection on OpenBSDAnton Lindqvist2020-08-061-0/+296
| | | | | | Regression introduced in commit cb93dc6a ("pkg/report: flag short uvm_fault reports as corrupted") causing some valid reports to be flagged as corrupted.
* pkg/report: flag short uvm_fault reports as corruptedAnton Lindqvist2020-07-274-1/+11
| | | | | | | They don't contain enough context to be useful. This change makes `testdata/openbsd/report/0` to be treated as corrupted, which is desirable since it also lacks context.
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-28 08:22:44 +0000