aboutsummaryrefslogtreecommitdiffstats
path: root/pkg/report
Commit message (Collapse)AuthorAgeFilesLines
...
* pkg/report: ignore xfs-printed warningsTaras Madan2025-05-022-0/+11
| | | | Closes #5968
* pkg/report: strip the __se_sys_ prefixAleksandr Nogikh2025-04-153-1/+68
| | | | | It will reduce the amount of duplicated reports. See #5940.
* pkg/report: include partially stripped prefixes to alt titlesAleksandr Nogikh2025-04-1542-40/+204
| | | | | It will help avoid bug duplication in case of adding new prefixes to strip.
* pkg: use kernelDir instead of 3 parametersTaras Madan2025-03-276-27/+28
| | | | It allows to reduce parameters count for some functions.
* pkg/symbolizer: introduce Symbolizer interfaceTaras Madan2025-03-074-36/+36
| | | | To simplify interface Read*Symbols were moved out from symbolizer.Symbolizer.
* all: remove loop variables scopingTaras Madan2025-02-171-1/+0
|
* pkg/report: ignore some timer-related framesAleksandr Nogikh2025-02-123-0/+402
| | | | | This will untangle the crashes of https://syzkaller.appspot.com/bug?extid=bf36934adc7979488192
* all: use min/max functionsDmitry Vyukov2025-01-171-5/+3
| | | | They are shorter, more readable, and don't require temp vars.
* pkg/report: ignore _INFO:Aleksandr Nogikh2025-01-032-2/+46
| | | | | | | 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-122-0/+63
| | | | Currently we mis-parse all of them, and attribute the bug to HWASAN.
* pkg/report: skip get_taint and put_deviceAleksandr Nogikh2024-12-052-0/+73
| | | | | These frames are not very informative. See https://syzkaller.appspot.com/bug?extid=72d3b151aacf9fa74455
* pkg/report: ignore one more informational warningAleksandr Nogikh2024-12-052-1/+24
| | | | | | | 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-052-0/+24
|
* pkg/report: detect the lost connection crash typeAleksandr Nogikh2024-12-031-0/+1
|
* pkg/report: ignore the drop_nlink frameAleksandr Nogikh2024-11-182-0/+117
| | | | | | | 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-152-1/+65
| | | | | | | | 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-302-0/+8
| | | | | These are just warnings to the system administrator. Ignore them during fuzzing.
* pkg/report: improve Bad page state parsingAleksandr Nogikh2024-10-225-3/+246
| | | | 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-232-1/+7
| | | | | | 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-104-2/+12
| | | | | | | | | | | 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: support module format with stacktrace_build_idJoey Jiao2024-09-032-1/+14
| | | | | Call trace can have line like below printed by %pSb: func_name+0x254/0x5f0 [module_name b31b29679ab712c360bddd861f655ab24898b4db]
* pkg/report: ignore rhashtable_lookup framesAleksandr Nogikh2024-08-302-0/+320
| | | | | | Bugs are unlikely to be in the rhashtable code itself. Example: https://syzkaller.appspot.com/bug?extid=128aaac913636290e5a9
* pkg/report: refactor parse testsAleksandr Nogikh2024-08-221-51/+71
| | | | The linter is complaining about a too high code complexity.
* pkg/report: extract the syz-executor infoAleksandr Nogikh2024-08-226-6/+46
| | | | | For Linux bugs, extract the proc id and the prog id from the crash report.
* pkg/report: remove args which already in ctxJoey Jiao2024-07-232-8/+5
|
* pkg/report: cleanPath for frame.FileJoey Jiao2024-07-231-4/+3
|
* pkg/report: support to symbolize line with module+offsetJoey Jiao2024-07-233-19/+116
|
* 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-013-0/+12
| | | | | | 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-243-19/+19
| | | | | | | 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-175-7/+508
| | | | | 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-142-0/+99
| | | | See https://syzkaller.appspot.com/bug?extid=6cf577c8ed4e23fe436b
* pkg/report: ignore __fortify_reportAleksandr Nogikh2024-06-142-0/+41
| | | | This is a too generic frame.
* sys/targets: mark big-endian targetsDmitry Vyukov2024-06-041-9/+3
| | | | | | Litte-endian is kind of default (except for s390). So instead of saying that each arch is litte-endian, mark only s390 as big-endian.
* sys/targets: add consts for gvisor/starnixDmitry Vyukov2024-05-271-3/+3
| | | | | Lint started warning about duplicate "gvisor" const in pkg/cover. Add gvisor/starnix consts to sys/targets package to avoid duplication.
* syz-ci: switch to using syz-manager for smoke testingDmitry Vyukov2024-05-211-0/+2
| | | | | Add smoke testing mode to manager and use it in syz-ci instead of pkg/instance which uses syz-fuzzer binary.
* pkg/report: ignore __phys_addrAleksandr Nogikh2024-05-032-0/+90
| | | | | | | 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
* tools/syz-linter: check t.Logf/Errorf/Fatalf messagesDmitry Vyukov2024-04-173-12/+12
| | | | | Fix checking of Logf, it has string in 0-th arg. Add checking of t.Errorf/Fatalf.
* pkg/report: remove unnecessary NewScan() callsAleksandr Nogikh2024-04-154-37/+45
| | | | | These are susceptible to potentially very long lines in the input. Direct splitting by \n is more reliable.
* pkg/report: fix OOB in linux.symbolize()Aleksandr Nogikh2024-04-151-16/+5
| | | | | | | | | | | | | NewScanner() had an implicit limit on the maximum line size, which we could surpass e.g. by printing some long serialized program. In this case, there's no reason to use NewScanner() -- we already have the whole buffer, so let's use raw byte operations instead. Remove one of the checks that turned out to be unneeded, but leave an assertion inside the symbolize() method. Closes #4198.
* all: remove akaros supportDmitry Vyukov2024-04-1511-641/+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: add more assertionsAleksandr Nogikh2024-04-101-0/+17
| | | | It should hopefully help debug #4198.
* pkg/report: make "mand mount option" regexps more robustAleksandr Nogikh2024-04-102-1/+5
| | | | | | 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/symbolizer: add Cache typeDmitry Vyukov2024-04-021-1/+5
| | | | | | | | When the same crash happens all over again, we repeatedly symbolize the same PCs. This is slow and blocks VM loop in the manager. Cache PCs we already symbolize, we are likely to symbolize them again.
* pkg/report: capture starnix kernel panics caused by rust panicsLaura Peskin2024-03-073-17/+476
| | | | | | | | | | 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.
* syz-manager: truncate repro logs before reportingAleksandr Nogikh2024-02-212-0/+36
| | | | | Until we have figured out a way to solve #4495, let's just truncate repro logs before sending them over the dashboard API.
* pkg/report: ignore ida_freeAleksandr Nogikh2024-02-152-0/+107
| | | | | | 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-232-0/+30
| | | | These are just informative messages.
* pkg/report/freebsd.go: nolint goconst for freebsdOopsesTaras Madan2023-10-261-0/+1
| | | | To unblock #4285.
* pkg/report: ignore strstr()Alexander Potapenko2023-09-042-0/+34
| | | | | Like many other str* functions, strstr() is not interesting and should be ignored.
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-12 15:44:08 +0000