aboutsummaryrefslogtreecommitdiffstats
path: root/pkg/report/testdata/linux
Commit message (Collapse)AuthorAgeFilesLines
* pkg/report: skip get_taint and put_deviceAleksandr Nogikh2024-12-051-0/+71
| | | | | These frames are not very informative. See https://syzkaller.appspot.com/bug?extid=72d3b151aacf9fa74455
* pkg/report: ignore one more informational warningAleksandr Nogikh2024-12-051-0/+23
| | | | | | | Prevent syzkaller from reacting to: "warning: `syz.1.261' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211".
* pkg/report: ignore the "uses deprecated v2 capabilities" warningAleksandr Nogikh2024-12-051-0/+23
|
* pkg/report: ignore the drop_nlink frameAleksandr Nogikh2024-11-181-0/+116
| | | | | | | It's a helper used by many different filesystems. Let's be more specific. https://syzkaller.appspot.com/bug?extid=651ca866e5e2b4b5095b
* pkg/report: improve "Bad page state" parsingDmitry Vyukov2024-11-151-0/+64
| | | | | | | | We've got a dup: https://syzkaller.appspot.com/bug?extid=d6f5b7a41831ca1a99a0 for an exising report: https://syzkaller.appspot.com/bug?extid=be32baeb2433f286bc24
* pkg/report: ignore warnings printed by __ext4_msgAleksandr Nogikh2024-10-301-0/+7
| | | | | These are just warnings to the system administrator. Ignore them during fuzzing.
* pkg/report: improve Bad page state parsingAleksandr Nogikh2024-10-224-1/+230
| | | | Take a frame from the stack trace that is included in the bug report.
* pkg/report: better suppress ALSA-caused go runtime errorAleksandr Nogikh2024-09-231-1/+6
| | | | | | Sometimes it may happen that we only get part of the string. Let's suppress the report both for the specific error message and for ALSA in general.
* pkg/report: filter out false reboot reportsSabyrzhan Tasbolatov2024-09-103-0/+10
| | | | | | | | | | | Strict regexp rules to avoid false reboot reports as "Booting the kernel." should always start from the start and at the end of line. Also addressed in unit test the previous fix in https://github.com/google/syzkaller/commit/026e2200. Fixes: https://github.com/google/syzkaller/issues/3955
* pkg/report: ignore rhashtable_lookup framesAleksandr Nogikh2024-08-301-0/+319
| | | | | | Bugs are unlikely to be in the rhashtable code itself. Example: https://syzkaller.appspot.com/bug?extid=128aaac913636290e5a9
* pkg/report: extract the syz-executor infoAleksandr Nogikh2024-08-223-0/+3
| | | | | For Linux bugs, extract the proc id and the prog id from the crash report.
* pkg/report: add new Linux rcu stall report formatDmitry Vyukov2024-07-023-0/+555
| | | | These are mis-parsed for now. Just add test cases.
* pkg/report: suppress executor SIGBUSDmitry Vyukov2024-07-012-0/+11
| | | | | | SIGBUS means OOM on Linux. Most of the crashes that happen during fuzzing are SIGBUS, so separate them from SIGSEGV and suppress.
* pkg/report: ignore cleanup_srcu_structAleksandr Nogikh2024-06-141-0/+98
| | | | See https://syzkaller.appspot.com/bug?extid=6cf577c8ed4e23fe436b
* pkg/report: ignore __fortify_reportAleksandr Nogikh2024-06-141-0/+40
| | | | This is a too generic frame.
* pkg/report: ignore __phys_addrAleksandr Nogikh2024-05-031-0/+89
| | | | | | | This is not the place of the actual bug. We end up collecting too many different reports in one place: https://syzkaller.appspot.com/bug?extid=daa1128e28d3c3961cb2
* pkg/report: make "mand mount option" regexps more robustAleksandr Nogikh2024-04-101-0/+4
| | | | | | In some cases, we may only collect a part of the kernel output. There are no other "mand mount option" warnings in the kernel, so let's match by a shorter regexp.
* pkg/report: ignore ida_freeAleksandr Nogikh2024-02-151-0/+106
| | | | | | This library method is used in multiple places throughout the kernel. Sample bug: https://syzkaller.appspot.com/bug?extid=dfab1425afcdae5ac970
* pkg/report: ignore CPU bug mitigation warningsAleksandr Nogikh2023-11-231-0/+28
| | | | These are just informative messages.
* pkg/report: ignore strstr()Alexander Potapenko2023-09-041-0/+33
| | | | | Like many other str* functions, strstr() is not interesting and should be ignored.
* pkg/report: ignore copy_page_{to,from}_iter(), copy_folio_to_iter()Alexander Potapenko2023-09-041-0/+88
| | | | | | | | | Bug title in https://syzkaller.appspot.com/bug?extid=17a061f6132066e9fb95 is "KMSAN: kernel-infoleak in copy_page_to_iter (4)", which is too generic and may potentially correspond to multiple bugs. Ignore copy_page_to_iter() and copy_folio_to_iter() to make it more meaningful. In addition, speculatively ignore copy_page_from_iter().
* pkg/report: drop "ALT: KMSAN origin" titles for uninit reportsAlexander Potapenko2023-08-3120-20/+0
| | | | | | | | | | | | | | | | | | | | | | | | It was initially proposed in https://github.com/google/syzkaller/issues/1575 that KMSAN reports with the same origin should be clustered together using an alt title. This however turns out to be too aggressive: certain KMSAN reports have their uninitialized values originating from common functions - this leads to too many KMSAN reports being glued together. Because KMSAN reports can be also clustered with KASAN reports or other kernel panics, ultimately seemingly unrelated crashes are considered similar just because they share their top frames with two KMSAN reports that, in turn, share the same origin. The resulting issues on the dashboard look confusing to the users, they are hard to find and require manual untangling, which probably outweighs the benefits of having KMSAN issues with exactly the same origin clustered together. For other types of KMSAN reports (infoleaks and use-after-frees) the alt titles are preserved. First, there are fewer of those on the dashboard. Second, they are rarely grouped together with non-KASAN reports and are less likely to cause a lot of mess.
* pkg/report: gather Go runtime bugs under one bugFlorent Revest2023-07-263-0/+23
| | | | | | | | | | | | | | | | | | | | | | | When a "fatal error:" bug is reported, this usually means that syzkaller itself had a memory corruption (except in the gVisor fuzzing case where this could be an actual bug in gVisor) Most likely, this is due to a kernel that went wild and corrupted the syzkaller address space, but in that case the exact details of what part of the runtime failed are rarely relevant. This gathers all these go runtime errors under one umbrella so they are easier to track. Except for gVisor on which the logic is kept the same as existing. Add three test cases to the linux reporting: - 705 (equivalent to the current all/report/7) to make sure Go OOO are suppressed (they have a different title now but still get suppressed) - 706 (equivalent to the current all/report/8) to make sure that ALSA "fatal errors" are not handled as Go fatal errors - 707 (new) to make sure that reports like https://syzkaller.appspot.com/bug?extid=3f00d7083c52713ba3b0 are re-named to "go runtime error"
* pkg/report: update decompile testsAleksandr Nogikh2023-07-112-3/+3
| | | | Newer arm compiler versions produce somewhat different output.
* pkg/report: introduce crash.SyzFailure report typeAleksandr Nogikh2023-07-062-0/+2
| | | | It refers to SYZFAIL and SYZFATAL errors.
* pkg/report: extract more report types for LinuxAleksandr Nogikh2023-07-05303-30/+311
| | | | Amend oops and oopsFormat to contain report type.
* pkg/report: skip more lib/xarray.h and mm/filemap.c functionsAleksandr Nogikh2023-07-041-0/+225
| | | | Reference: https://syzkaller.appspot.com/bug?extid=c370a63abf53498ae3e2
* pkg/report: whack-a-mole folio-related functionsAlexander Potapenko2023-07-045-0/+300
| | | | | | | | | | | | | | | | | Ignore the following functions: - folio_alloc - filemap_alloc_folio - __filemap_get_folio - find_or_create_page - do_read_cache_folio - read_cache_page - pagecache_get_page - grab_cache_page_write_begin that perform allocations within mm/filemap.c This is to defeat an overly eager report clusterization in https://syzkaller.appspot.com/bug?extid=828dfc12440b4f6f305d
* pkg/report: ignore crc_itu_tAleksandr Nogikh2023-06-131-0/+94
| | | | See https://syzkaller.appspot.com/bug?extid=d8fc21bfa138a5ae916d
* pkg/report: ignore print_taintedAleksandr Nogikh2023-06-131-0/+43
| | | | Sample bug: https://syzkaller.appspot.com/bug?extid=fae676d3cf469331fc89
* pkg/report: ignore Register information linesAleksandr Nogikh2023-05-201-0/+644
| | | | | | They are misleading guilty file detection. See https://groups.google.com/g/syzkaller-bugs/c/T6Z_5Gh1Qio
* pkg/report: ignore kvfreeAleksandr Nogikh2023-05-161-0/+98
| | | | Based on https://syzkaller.appspot.com/bug?extid=64b645917ce07d89bde5
* pkg/report: ignore arm64 fault handlingAleksandr Nogikh2023-05-101-0/+46
| | | | See https://syzkaller.appspot.com/bug?id=88b03615bcf53f3cdc9b987ad26207a9b8d47d8f
* pkg/report: skip stack trace handling functionsAleksandr Nogikh2023-04-171-0/+131
| | | | Also, skip more workqueue functions.
* pkg/report: ignore mm/folio-compat.c and (un)lock_pageAleksandr Nogikh2023-04-052-0/+119
|
* pkg/report: ignore arch/.*/kernel/unwind.*.c and kernel/stacktrace.cAleksandr Nogikh2023-04-031-0/+175
|
* pkg/report: ignore more guilty filesAleksandr Nogikh2023-03-282-1/+75
| | | | | Ignore arch/arm64/kernel/process.c and some of page cache sources, as the real problem will much more likely lie in the caller.
* pkg/report: skip the rcu_barrier frame for hung tasksAleksandr Nogikh2023-03-271-0/+75
| | | | Its caller is much more informative.
* pkg/report: fix false positive reboot reportsDmitry Vyukov2023-03-131-0/+7
| | | | | For context see: https://lore.kernel.org/all/CACT4Y+ZMXN=smH-0FN4Ui0zm6P-c=eEwG6fNJ9deTnc0M099UQ@mail.gmail.com/T/#t
* pkg/report: ignore copy_to/from_iterDmitry Vyukov2023-03-133-2/+122
|
* pkg/report: handle guilty file extraction for non-symbolized reportsAleksandr Nogikh2023-02-161-0/+116
| | | | | Currently we return ".", which is not really expected by all the surrounding logic.
* pkg/report: extract guilty files for arm64 rcu stallsAleksandr Nogikh2023-02-101-0/+81
|
* pkg/report: extract guilty files for rcu errors correctlyAleksandr Nogikh2023-02-102-0/+135
| | | | | | The existing code is broken - the console output does not contain a whitespace before the apic_timer_interrupt frame. Also, add the apic_timer source files to the excluded ones.
* pkg/report: improve rcu stall parsing on arm64Aleksandr Nogikh2023-02-101-0/+72
|
* pkg/report: anchor at netlink_dump frameAleksandr Nogikh2023-02-091-0/+112
| | | | This frame also ditributes work to other functions.
* pkg/report: test ReportToGuiltyFileAleksandr Nogikh2023-02-081-0/+67
| | | | | | | Refactor the existing guilty path testing code to allow for simpler extension. Reuse the resulting code to invoke guilty_raw tests.
* pkg/report: skip more memory allocation framesAleksandr Nogikh2023-02-062-2/+45
| | | | | The family of such functions is big and keeps on growing. Add them to the generic skipPatterns code.
* pkg/report: detect custom VFS errorsDmitry Vyukov2023-01-203-0/+9
| | | | Fixes #3621
* pkg/report: skip netlink_ack and netlink_rcv_skbAlexander Potapenko2023-01-172-0/+76
| | | | | | | Two KMSAN reports belonging to different subsystems ended up being merged together because they both had netlink_ack in their origin. Let's skip this frame as well as netlink_rcv_skb, which is common among several network protocols.
* pkg/report: ignore kvmalloc framesDmitry Vyukov2022-11-281-0/+72
|
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-27 21:02:06 +0000