aboutsummaryrefslogtreecommitdiffstats
path: root/pkg/report/testdata/linux
Commit message (Collapse)AuthorAgeFilesLines
* pkg/report: ignore more frames for warnings in usb_submit_urbAndrey Konovalov2019-05-291-0/+105
|
* pkg/report: improve usb_submit_urb report titlesAndrey Konovalov2019-05-272-0/+166
|
* pkg/report: add Type/Frame to ReportDmitry Vyukov2019-05-2090-1/+90
| | | | | | In several places we do special handling for some crash types. Currently we compare report title with magic strings, which is error-prone. Add explicit Type to reports.
* pkg/report: Label powerpc unreliable stack frames as questionableAndrew Donnellan2019-05-171-0/+31
| | | | | | | Add a second "questionable" regex to match the powerpc "(unreliable)" format. Signed-off-by: Andrew Donnellan <ajd@linux.ibm.com>
* pkg/report: Add powerpc's __switch_to to function skip listAndrew Donnellan2019-05-171-1/+1
| | | | Signed-off-by: Andrew Donnellan <ajd@linux.ibm.com>
* pkg/report: preserve trackback from other CPUsDmitry Vyukov2019-05-103-2/+863
| | | | | | | | For some bug types kernel produces traceback of all CPUs (which is presumably useful for these crashes). However, we currently throw it away because it has context different from the oops context. Detect such traceback and preserve output.
* pkg/report: improve format of "locking bug" reportsDmitry Vyukov2019-05-092-0/+91
|
* pkg/report: add new format of kernel page faultsDmitry Vyukov2019-05-091-0/+65
|
* pkg/report: don't mark unknown oopses as corruptedAndrey Konovalov2019-05-084-5/+16
|
* pkg/report: improve warning titlesAndrey Konovalov2019-05-0712-11/+118
| | | | | This change makes the reporting code account for the skip patterns when selecting the frame that is used in a title of a generic warning report.
* pkg/report: Handle powerpc stack traces correctlyAndrew Donnellan2019-05-072-0/+45
| | | | | | | powerpc stack traces are printed a bit differently from x86 stack traces. Adjust the regexes accordingly to cope with this format. Signed-off-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
* pkg/report: improve titles of 'sleeping function called from invalid context'Andrey Konovalov2019-05-062-1/+89
|
* pkg/report: add __ia32_sys_ syscall prefixDmitry Vyukov2019-05-031-0/+63
|
* pkg/report: skip printk and other printing functionsAndrey Konovalov2019-05-033-1/+283
|
* pkg/report: fix stalls in RIP frameDmitry Vyukov2019-04-241-0/+73
| | | | | Even though we extract an anchor frame which usually higher up the stack, the anchor frame can be on RIP: line too. Account for that.
* pkg/report: skip osq_lock on linuxDmitry Vyukov2019-04-231-0/+65
| | | | Another new helper for locking.
* report: skip strscpy and read_word_at_a_time framesAndrey Konovalov2019-04-221-0/+51
|
* pkg/report: ignore 'down' frame in the call stackAndrey Konovalov2019-04-111-0/+80
|
* pkg/report: fix testDmitry Vyukov2019-04-091-1/+2
|
* pkg/report: add another interesting linux test caseDmitry Vyukov2019-04-091-0/+42
|
* pkg/report: refine stalls in compat ioctl'sDmitry Vyukov2019-04-092-41/+44
|
* pkg/report: refine hung task processing for v4.15Dmitry Vyukov2019-04-051-0/+91
|
* pkg/report: add a test for .PID removalDmitry Vyukov2019-04-051-0/+33
|
* pkg/report: add another linux testDmitry Vyukov2019-04-011-0/+186
|
* pkg/report: skip memmove on linuxDmitry Vyukov2019-03-241-0/+122
|
* pkg/report: skip memchr in linux reportsDmitry Vyukov2019-03-121-0/+58
|
* pkg/report: skip retpolines in reportsDmitry Vyukov2019-03-075-0/+311
| | | | These __x86_indirect_thunk_rax broke reports for bad indirect calls.
* executor: remove ability to detect kernel bugsDmitry Vyukov2019-01-311-3/+0
| | | | | | | | This ability was never used but we maintain a bunch of code for it. syzkaller also recently learned to spoof this error code with some ptrace magic (probably intercepted control flow again and exploited executor binary). Drop all of it.
* pkg/report: skip trylock functionsDmitry Vyukov2019-01-221-0/+165
| | | | Skip various *_trylock functions as we do for *_lock functions.
* pkg/report: more tuning for trusty reportsDmitry Vyukov2019-01-152-0/+92
| | | | Update #933
* pkg/report: add parsing of trusty crashesDmitry Vyukov2019-01-143-0/+108
| | | | Update #933
* pkg/report: strip trailing deadlock reportsDmitry Vyukov2019-01-141-0/+368
| | | | | | Oops messages frequently induce possible deadlock reports because oops reporting introduces unexpected locking chains. So if we have enough of the actual oops, strip the deadlock message.
* pkg/report: improve linux report parsing if we have contextsDmitry Vyukov2019-01-061-0/+186
| | | | | If we have contexts, we don't need to strip the first report at the beginning of the second report.
* pkg/report: support CONFIG_PRINTK_CALLERDmitry Vyukov2019-01-0314-0/+2500
| | | | | | | | | | | | | | | | | | CONFIG_PRINTK_CALLER has reached linux-next: https://groups.google.com/d/msg/syzkaller/xEDUgkgFvL8/d5bBS3BJBwAJ Enable CONFIG_PRINTK_CALLER and support parsing of its output format. This gives us several advantages: - output from different contexts don't intermix - intermixed output doesn't cause corrupted reports - we can keep larger prefix since we know it comes from the same task Credit for the kernel part goes to Tetsuo Handa. Also Sergey Senozhatsky and Petr Mladek for reviews of the kernel part. Fixes #596 Fixes #600
* pkg/report: account for new symbol suffixes produced by gcc9Dmitry Vyukov2018-12-312-0/+101
|
* pkg/report: improve parsing of "corrupted stack end detected inside scheduler"Dmitry Vyukov2018-12-306-1/+242
|
* pkg/report: improve double fault parsingDmitry Vyukov2018-12-307-0/+781
| | | | | | | | | | Ignore double faults as start of a second report. Double fault can happen during handling of paging faults if memory is badly corrupted. Also it usually happens synchronously, which means that maybe the report is not corrupted. But of course it can come from another CPU as well. Add more interesting test cases.
* pkg/report: parse linux stack corruption reportsDmitry Vyukov2018-12-303-0/+169
|
* pkg/report: skip strncpy in linux reportsDmitry Vyukov2018-12-121-0/+55
|
* pkg/report: refine rcu stall detectionDmitry Vyukov2018-11-221-0/+69
| | | | Add another anchor frame.
* pkg/report: fix corrupted stack trace checkingDmitry Vyukov2018-11-221-0/+1139
| | | | | | | | | | | | | | We started detecting all kernel reboots as corrupted, because we considered that after any "Allocated" line a stack trace should follow. Kernel boot output now contains: ima: Allocated hash algorithm: sha256 and there is no stack trace after that. 1. Refine stack trace regexps (we actually want to look for "Allocated by task PID:" lines). 2. Don't check stacks if report format says that it does not contain stacks.
* pkg/report: add "PANIC: double fault" report formatDmitry Vyukov2018-11-225-1/+164
| | | | | | | Amusing that's another kernel failure mode that we are discovering after 3 years. One can't even reliably understand when kernel has crashed. I wonder if syzkaller never hit these, or just never recognized and reported them. We will see. Don't even want to think about arm kernel output parsing.
* pkg/report: ignore arch/.*/mm/physaddr.c as guilty fileDmitry Vyukov2018-10-101-0/+51
| | | | | | | This is called from kfree in the added test. We already ignore everything related to kmalloc/free and e.g. arch/.*/mm/fault.c, so it looks reasonable to ignore this one too.
* pkg/report: ignore printk as guilty fileDmitry Vyukov2018-09-281-0/+103
|
* pkg/report: improve KMEMLEAK report parsingDmitry Vyukov2018-09-284-0/+95
| | | | Skip few more common allocation functions.
* pkg/report: fix guilty file extractionDmitry Vyukov2018-09-262-0/+78
| | | | | Account for the case that some file names can appear _before_ crash report starts. Start extracting guilty file starting from StartPos.
* pkg/report: ignore more str* functionsDmitry Vyukov2018-09-243-0/+555
|
* pkg/report: improve KMSAN report parsingDmitry Vyukov2018-09-138-6/+218
| | | | | | Extract guilty frame from stack. Add few more ignored functions. Add more tests.
* pkg/report: improve rcu stall/lockup reportsDmitry Vyukov2018-09-1046-471/+2093
| | | | | | | | | | | | | | | | During rcu stalls and cpu lockups kernel loops in some part of code, usually across several functions. When the stall is detected, traceback points to a random stack within the looping code. We generally take the top function in the stack (with few exceptions) as the bug identity. As the result stalls with the same root would produce multiple reports in different functions, which is bad. Instead we identify a representative function deeper in the stack. For most syscalls it can be the syscall entry function (e.g. SyS_timer_create). However, for highly discriminated functions syscalls like ioctl/read/write/connect we take the previous function (e.g. for connect the one that points to exact protocol, or for ioctl the one that is related to the device). Fixes #710
* pkg/report: ignore mm/memory.c as guilty fileDmitry Vyukov2018-08-291-0/+61
|
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-04-05 23:18:40 +0000