aboutsummaryrefslogtreecommitdiffstats
path: root/pkg/report/testdata
Commit message (Collapse)AuthorAgeFilesLines
* pkg/report: exclude crc implementations from guilty filesAleksandr Nogikh2025-07-211-0/+101
| | | | | | | If these happen to be in the stack frames, in almost all cases it will be due to a bug in the calling code. See the discussion in #5784.
* pkg/report: update testdataTaras Madan2025-07-0914-2/+14
|
* pkg/report: update testdataTaras Madan2025-07-0810-10/+10
|
* pkg/report: update testdataTaras Madan2025-07-0410-14/+14
|
* pkg/report: split crash.KCSANTaras Madan2025-07-034-3/+36
| | | | | Introduce crash.KCSANAssert. Introduce crash.KCSANUnknown.
* pkg/report: update testdata typesTaras Madan2025-07-032-2/+2
|
* pkg/report: update testdata typesTaras Madan2025-07-0323-23/+23
|
* pkg/report: update testdata files typesTaras Madan2025-07-0384-85/+85
|
* pkg/report: update testdata report typesTaras Madan2025-07-02198-19/+202
|
* pkg/report/testdata/linux: add TYPE: KFENCETaras Madan2025-06-2710-0/+10
| | | | Run `go test ./pkg/report -update`.
* pkg/report/testdata: update KMSAN reportsTaras Madan2025-06-2023-0/+23
|
* pkg/report: improve Rust report parsingAleksandr Nogikh2025-06-202-0/+222
| | | | | | | We need to look for the error type after the "rust_kernel: panicked" line. Ignore some common irrelevant frames.
* pkg/report: demangle Rust reportsAleksandr Nogikh2025-06-182-0/+477
| | | | | | | | Do demangling as a part of Symbolize() processing. Add a TestSymbolize test to verify the results. Fix old report_test.go bugs to better react to the -update flags. Closes #6035.
* pkg/report: ignore the __alloc_frozen_pages_noprof frameAleksandr Nogikh2025-06-172-0/+139
| | | | | | | | | | Even though __alloc_frozen_pages_noprof has the WARN_ON, the actual problem lies in how malloc was called down the stacktrace. This leads to several different bugs being merged into one: https://syzkaller.appspot.com/bug?extid=03fb58296859d8dbab4d Ingore the __alloc_frozen_pages_noprof frame when selecting the bug title.
* pkg/report: parse the new WARNING formatAleksandr Nogikh2025-06-172-0/+336
| | | | | | | | The format has been slightly changed lately and we have started to get duplicates of the exiting reports, e.g. https://syzkaller.appspot.com/bug?extid=077d9ebda84f426a6a1e Adjust the parsing rules to keep the resulting bug titles unchanged.
* pkg/report: skip the folio_unlock frameAleksandr Nogikh2025-06-112-0/+166
| | | | | | | It's too generic and leads to merging unrelated crash reports. See https://syzkaller.appspot.com/bug?extid=c0dc46208750f063d0e0 and the related LKML discussion.
* pkg/report: add test for __list_add_valid_or_reportMarco Elver2025-05-191-0/+152
| | | | | The DEBUG_LIST/LIST_HARDENED changed the internal symbol names. Add a test so that this does not regress.
* pkg/report: ignore xfs-printed warningsTaras Madan2025-05-021-0/+10
| | | | Closes #5968
* pkg/report: strip the __se_sys_ prefixAleksandr Nogikh2025-04-152-1/+67
| | | | | It will reduce the amount of duplicated reports. See #5940.
* pkg/report: include partially stripped prefixes to alt titlesAleksandr Nogikh2025-04-1540-0/+76
| | | | | It will help avoid bug duplication in case of adding new prefixes to strip.
* pkg/report: ignore some timer-related framesAleksandr Nogikh2025-02-122-0/+398
| | | | | This will untangle the crashes of https://syzkaller.appspot.com/bug?extid=bf36934adc7979488192
* pkg/report: ignore _INFO:Aleksandr Nogikh2025-01-031-0/+45
| | | | | | | These can lead to false positives when BPF debugging data is printed, e.g. [ 461.316169][ T3168] [U] [1] INVALID BTF_INFO:72000001
* pkg/report: fix parsing of HWASAN reportsDmitry Vyukov2024-12-121-0/+62
| | | | Currently we mis-parse all of them, and attribute the bug to HWASAN.
* 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.
* executor: add runner modeDmitry Vyukov2024-06-241-15/+15
| | | | | | | Move all syz-fuzzer logic into syz-executor and remove syz-fuzzer. Also restore syz-runtest functionality in the manager. Update #4917 (sets most signal handlers to SIG_IGN)
* pkg/report: support prettified starnix logsLaura Peskin2024-06-174-2/+502
| | | | | Also updates the title template for starnix kernel panics to use dashboard space a little more efficiently.
* 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
* all: remove akaros supportDmitry Vyukov2024-04-159-445/+0
| | | | | | | Akaros support is unused, it was shutdown on syzbot for a while, the akaros development seems to be frozen for years as well. We have a bunch of hacks for Akaros since it supported only super old gcc and haven't supported Go. Remove it.
* 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: capture starnix kernel panics caused by rust panicsLaura Peskin2024-03-072-0/+369
| | | | | | | | | | Forms a reasonable title for reports of starnix crashes caused by rust panics in the starnix kernel, and takes a first pass at capturing function / pointer details from the backtrace while discarding most of the unrelated log lines. Also splits the fuchsia reporter data inputs into two parts, one for zircon and one for starnix.
* 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-264-0/+21
| | | | | | | | | | | | | | | | | | | | | | | 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"
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-18 00:59:58 +0000