aboutsummaryrefslogtreecommitdiffstats
path: root/pkg/report/testdata/linux
Commit message (Collapse)AuthorAgeFilesLines
...
* pkg/report: improve report titlesAndrey Konovalov2020-03-091-0/+167
|
* pkg/report: update parsing of rcu stalls in ioctlsDmitry Vyukov2020-02-021-0/+52
| | | | vfs_ioctl is now inlined somethimes...
* pkg/report: don't attribute deadlocks to workqueue functionsDmitry Vyukov2020-01-314-2/+200
| | | | | In all cases we seen deadlocks in workqueue functions are related to the subsystem that submits work items.
* pkg/report: treat nfnetlink_rcv_msg as anchor frameDmitry Vyukov2020-01-204-0/+223
| | | | | | There is tremendous branching after that frame to all existing netlink callbacks which are effectively completely different syscalls.
* pkg/report: add pattern for Linux #SS faultsJann Horn2020-01-151-0/+38
| | | | | | | | | | | | | | | | | | | | On X86-64, dereferencing a non-canonical address normally causes a #GP, for which syzkaller already has a pattern. However, if the base register of the non-canonical address is RBP (which can happen in builds that use RBP as a general-purpose register because they don't use frame pointer unwinding), #SS is thrown instead, for which syzkaller did not yet have a pattern. To see this kind of fault, you can insert the following code in kernel_init() after the call to rcu_end_inkernel_boot(): asm volatile( "movabs $0x8000000000000000, %rbp\n\t" "movq (%rbp), %rax\n\t" "ud2\n\t" ); Linux prints a different error message for #SS, so add that error message to syzkaller's list of patterns.
* pkg/report: add more ignored framesAndrey Konovalov2020-01-071-0/+129
|
* pkg/report: fix guilty file extraction in presence of rcu stallsDmitry Vyukov2019-12-051-0/+165
| | | | | | | | | | | | | | The the added test for exception from exception corner case. "BUG: spinlock lockup" fails to respect panic_on_warn and panic after printing report (though, it's a BUG already, so it should have been paniced even without panic_on_warn). As the result we got "spinlock lockup" followed by "rcu stall" report. And we have that special exception for rcu stalls b/c for them the most of the report is irrelevant up to apic_timer_interrupt frame. The code did not expect this weird double-report case and skipped everything up to apic_timer_interrupt, though it's actually a lockup in netfilter code.
* pkg/report: improve reports titlesAndrey Konovalov2019-12-051-0/+86
| | | | Ignore kobject_put in stack frames.
* pkg/report: improve report titlesAndrey Konovalov2019-11-291-0/+68
|
* pkg/report: add few more UBSAN reportsDmitry Vyukov2019-11-293-0/+102
| | | | Update #1523
* pkg/report: update UBSAN report parsingDmitry Vyukov2019-11-285-3/+53
| | | | Update #1523
* pkg/report: generalize general protection fault patternJann Horn2019-11-192-0/+107
| | | | | | | | | | | | An upcoming patch for Linux will change the error reporting pattern for general protection faults such that the colon doesn't necessarily come immediately after the string "general protection fault" (see https://lore.kernel.org/lkml/20191118142144.GC6363@zn.tnic/). Change the pattern in syzkaller before that happens. Note that this is not necessarily the final format; in particular, the ordering of the KASAN note and the "general protection fault" line might swap.
* pkg/report: ignore boot warning that always happensDmitry Vyukov2019-11-081-0/+316
| | | | | | | Happens on every boot and prevents detection of other bugs. The warning was already reported upstream: https://groups.google.com/forum/#!msg/syzkaller-bugs/8HZdIbi8sdE/Niu4qijeAAAJ https://syzkaller.appspot.com/bug?extid=4d497898effeb1936245
* pkg/report: trim panic_on_warn set few lines earlierDmitry Vyukov2019-11-081-0/+81
| | | | | The KCSAN reports can be quite short. Now with task contexts we can hopefully reduce the threshold a bit.
* pkg/report: fix up panic handlingDmitry Vyukov2019-11-061-0/+72
| | | | Obviously there is an exception to every exception in kernel output parsing...
* pkg/report: better diffirentiate task hung reportsDmitry Vyukov2019-10-232-0/+385
| | | | A number of hangs happen when trying to cancel tasks in different subsystems.
* syz-fuzzer, executor: Add support for blacklisting data race framesMarco Elver2019-10-222-2/+6
| | | | | This adds support to add frames that have already been in data races, to the KCSAN report blacklist.
* pkg/report: improve parsing of task hung reportsDmitry Vyukov2019-10-2216-2/+3099
| | | | | | | | | The problem with task hung reports is that they manifest at random victim stacks, rather at the root cause stack. E.g. if there is something wrong with RCU subsystem, we are getting hangs all over the kernel on all synchronize_* calls. So before resotring to the common logic of skipping some common frames, we look for 2 common buckets: hangs on synchronize_rcu and hangs on rtnl_lock and group these together.
* pkg/report: Add ppc64le kernel paging request test caseAndrew Donnellan2019-10-141-0/+42
| | | | Signed-off-by: Andrew Donnellan <ajd@linux.ibm.com>
* pkg/report: fix up testDmitry Vyukov2019-10-081-0/+1
|
* pkg/report: ignore mutex_slowlock in task hung reportsDmitry Vyukov2019-10-081-0/+270
|
* pkg/report: fix ODEBUG parsing for v4.4Dmitry Vyukov2019-10-071-0/+80
|
* pkt/report: Shorten KCSAN report titlesMarco Elver2019-10-042-0/+59
|
* pkg/report: improve USB reportsAndrey Konovalov2019-09-251-0/+64
|
* pkg/report: improve USB reportsAndrey Konovalov2019-09-251-1/+1
| | | | tty_unregister_device looks generic enough, add to ignore list.
* pkg/report: improve USB report titlesAndrey Konovalov2019-09-244-0/+427
|
* pkg/report: add a test case which we mis-handle nowDmitry Vyukov2019-09-201-0/+266
|
* pkg/report: ignore "INFO: recovery required on readonly filesystem"Dmitry Vyukov2019-09-171-0/+7
| | | | This is not a kernel bug.
* pkg/report: improve some USB reportsAndrey Konovalov2019-09-174-0/+395
|
* pkg/report: update ODEBUG warning formatDmitry Vyukov2019-09-041-0/+54
| | | | It seems something has changed in the kernel again...
* pkg/report: improve USB reports (#1372)Andrey Konovalov2019-09-032-0/+224
|
* pkg/report: revert bucketing MAX_STACK_TRACE_ENTRIES reports (#1357)Andrey Konovalov2019-08-222-2/+2
| | | | | 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.
* pkg/report: improve netdev reports titlesAndrey Konovalov2019-08-212-0/+189
|
* pkg/report: ignore finish_wait frameAndrey Konovalov2019-08-191-0/+155
|
* pkg/report: improve ODEBUG titlesAndrey Konovalov2019-08-151-0/+62
|
* pkg/report: improve some titles (#1332)Andrey Konovalov2019-08-137-1/+422
| | | | | | * pkg/report: improve BUG: MAX_STACK_TRACE_ENTRIES titles * pkg/report: improve refcount bug titles
* pkg/report: add KMSAN kernel-usb-infoleak testsAndrey Konovalov2019-08-082-0/+199
|
* pkg/report: ignore flush_work related framesAndrey Konovalov2019-08-083-1/+110
|
* pkg/report: support older format of "bad usercopy"Dmitry Vyukov2019-07-221-0/+40
|
* pkg/report: support new format of "held lock freed" linux bugsDmitry Vyukov2019-07-162-0/+188
|
* pkg/report: ignore __wake_up function on linuxDmitry Vyukov2019-07-022-1/+251
| | | | They are very generic and a bug is almost always in the parent frame.
* pkg/report: fix up parsing of lockdep stacksDmitry Vyukov2019-06-231-0/+85
|
* pkg/report: improve should_fail regexpDmitry Vyukov2019-06-061-0/+144
| | | | | Some kernels print hex PC value before frames. Account for that in should_fail-matching regexp.
* pkg/report: skip refcount_* functionsDmitry Vyukov2019-06-042-0/+238
| | | | These are too generic and don't point to any subsystem. Skip them.
* pkg/report: add del_timer_sync to skip patternsAndrey Konovalov2019-06-031-0/+51
|
* 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>
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-25 00:50:24 +0000