aboutsummaryrefslogtreecommitdiffstats
path: root/pkg/report
Commit message (Collapse)AuthorAgeFilesLines
* pkg/report: ignore timer-related and mark_buffer_dirty framesGrigory Bazilevich2 days6-762/+328
| | | | | | | Fix corresponding test, remove incorrect tests Signed-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru> Signed-off-by: Denis Efremov <efremov@ispras.ru>
* pkg/report: extract whether kernel has panickedAleksandr Nogikh2026-01-29246-2/+264
|
* pkg/report: add test for condition string and special riscv stack trace matchingPimyn Girgis2026-01-271-0/+31
|
* pkg/report: detect warnings containing a condition stringPimyn Girgis2026-01-271-0/+5
| | | | Add a new regex to detect Linux warnings of the form "WARNING: [condition] file:line at func...".
* pkg/report: improve RISC-V stack trace detectionPimyn Girgis2026-01-271-1/+7
| | | | | In RISC-V, if show_regs() is called from kernel space, the stack is dumped without a proper indicator. Match the last line printed by show_regs() as a stack start indicator and do not treat the missing stack trace as a log corruption.
* pkg/report: double-free is at least as severe UAF writeTamás Koczka2026-01-262-3/+3
| | | | | | | | | | | Double-free is at least as severe as a UAF write because in case of UAF write, the vulnerable object is given and you have to find the right victim object - the writable offset and size needs to match. In case of double-free you can choose both your victim and attacker object, giving more options for a successful exploitation (there are attacker objects which can basically write all offset and sizes). This assumes that double-free is controlled in a way that the attacker can spray a victim object between the two `kfree()`s.
* pkg/report: refactor to remove nolintTaras Madan2026-01-231-2/+3
|
* pkg/aflow/flow/assessment: add UAF moderation workflowDmitry Vyukov2026-01-121-0/+4
| | | | | | Add workflow that can be used for moderation of UAF bugs (consistent/actionable reports), such UAF bugs can be upstreammed automatically, even if they happened only once and don't have a reproducer.
* pkg/report: move TitleToCrashType to crash packageDmitry Vyukov2026-01-097-63/+62
| | | | | | | | | TitleToCrashType is a simple function with no heavy dependencies that is used by the dashboard app. Currnetly we have to import pkg/report into dashboard/app, and this package has lots of heavy deps (symbolizer, demangler, coverage report generation, etc). Move TitleToCrashType to pkg/report/crash (where it arguably belongs anyway).
* pkg/report: fix fuchsia ParseTaras Madan2026-01-091-3/+10
| | | | | rep.Output and rep.Report offsets are different because rep.Report is symbolized Fix converts offsets from symbolized version back to the raw version.
* pkg/report/testdata: regenerateTaras Madan2026-01-0930-32/+15
| | | | Update all the test files. I removed test.Equals() check to do it for all the files at once.
* pkg/report: tune tests generationTaras Madan2026-01-091-1/+7
| | | | | 1. We use empty TITLE and TITLE absence. Let's use TITLE absence by default. 2. FRAME header shouldn't be generated, only updated.
* all: remove unused nolint directivesDmitry Vyukov2026-01-022-2/+1
|
* pkg/report: use existing osutil helpers in titleStat codeDmitry Vyukov2026-01-022-34/+8
|
* pkg/report: ignore the fast_dput/dput framesPimyn Girgis2025-12-013-0/+123
| | | | | | | fast_dput and dput are too generic. This causes several different bugs to be merged into one. See: https://syzkaller.appspot.com/bug?extid=b74150fd2ef40e716ca2 Ingore the fast_dput/dput frames when selecting the bug title.
* pkg/report: adapt to the new WARN formatAleksandr Nogikh2025-11-264-5/+309
| | | | | | | | | The format has been changed recently: https://lore.kernel.org/all/20251110114633.202485143@infradead.org/ This commit addresses the duplicates we currently see among the linux-next bugs, but likely there are more. We'll fix it once we notice them.
* pkg/report: add test for kmemleak with crc hashPimyn Girgis2025-11-031-0/+36
| | | | KMEMLEAK now prints a crc hash. Add a test to ensure we can properly parse it.
* pkg/report: support optional CRC in backtrace linesPimyn Girgis2025-11-031-2/+3
| | | | | | | | At some point kmemleak started adding a CRC checksum to the "backtrace:" line in memory leak reports. The existing regular expression did not account for this, causing parsing to fail for these reports. Update the regex to make the CRC component optional, allowing reports both with and without the checksum to be parsed correctly.
* pkg/report: don't print empty FRAME in failing testsTaras Madan2025-10-301-5/+5
| | | | | There is no need to see empty FRAME: field content in failing pkg/report tests. This change allow us to remove 1 parameter.
* pkg/report: skip crypto frames for KMSAN reportsAleksandr Nogikh2025-10-133-3/+187
| | | | | | | | | This bug is at least one case where we merge several different KMSAN reports because they end up being triggered in the same generic code: https://syzkaller.appspot.com/bug?id=6290a184e96e8fb4b657700adcd243ef195113e1 Skip some common symbols from crypto/ so that the titles become more specific.
* pkg/manager: add Rank column with tooltips to the main pageTaras Madan2025-08-282-3/+47
|
* pkg/manager: store titles stat in the crash dirTaras Madan2025-08-282-0/+164
|
* pkg/manager: store tail reportsTaras Madan2025-08-282-0/+50
| | | | Send only the first report to dashboard.
* report: add "BUG on" oops entry for gVisorKonstantin Bogomolov2025-08-141-0/+11
| | | | | | Following https://github.com/google/gvisor/commit/b47d21ef21a6f59b8f574eebf83c7936880c1c0d syzkaller should look for this message type.
* vm: refactoringTaras Madan2025-08-071-1/+1
| | | | | 1. func Run optionally accepts the opts. 2. Some refactoring, more comments.
* pkg/report: exclude crc implementations from guilty filesAleksandr Nogikh2025-07-212-0/+103
| | | | | | | 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.
* all: apply linter auto fixesTaras Madan2025-07-171-4/+4
| | | | ./tools/syz-env bin/golangci-lint run ./... --fix
* pkg/report: typo fixAlexander Potapenko2025-07-141-1/+1
| | | | Replace "keep-sorter" with "keep-sorted" to fix the build-time warning.
* pkg/report: update testdataTaras Madan2025-07-0914-2/+14
|
* pkg/report: introduce null ptr crash typesTaras Madan2025-07-094-50/+66
|
* pkg/report: update testdataTaras Madan2025-07-0810-10/+10
|
* dashboard/app: sort bugs by impactTaras Madan2025-07-085-5/+200
| | | | | The impact score is deducted from the title. Impact is max(known_titles).
* pkg/report: update testdataTaras Madan2025-07-0410-14/+14
|
* pkg/report: split crash.KFENCETaras Madan2025-07-043-28/+76
|
* pkg/report: split crash.KCSANTaras Madan2025-07-036-6/+48
| | | | | Introduce crash.KCSANAssert. Introduce crash.KCSANUnknown.
* pkg/report: remove spaces at the endTaras Madan2025-07-031-11/+11
| | | | We don't really need them.
* pkg/report: update testdata typesTaras Madan2025-07-032-2/+2
|
* pkg/report: use crash.KASANUnknown instead of crash.KASANOtherTaras Madan2025-07-032-9/+11
| | | | | | What we need is the category for "matched unknown KASAN bug". This king on bugs should be recategorised. The final goal is to keep this category empty.
* pkg/report: update testdata typesTaras Madan2025-07-0323-23/+23
|
* pkg/report: split crash.KMSANTaras Madan2025-07-032-4/+30
|
* pkg/report: update testdata files typesTaras Madan2025-07-0384-85/+85
|
* pkg/report: split crash.KASAN into partsTaras Madan2025-07-032-18/+82
| | | | We want to prioritize KASAN bugs differently.
* pkg/report: update testdata report typesTaras Madan2025-07-02198-19/+202
|
* dashboard/app: use crash types instead, no regexpsTaras Madan2025-07-025-22/+107
|
* pkg/report/testdata/linux: add TYPE: KFENCETaras Madan2025-06-2710-0/+10
| | | | Run `go test ./pkg/report -update`.
* pkg/report: add crash.KFENCE typeTaras Madan2025-06-272-4/+5
|
* pkg/report: factor out type definitionsTaras Madan2025-06-2711-181/+256
|
* pkg/report: minor refactoringTaras Madan2025-06-202-22/+22
| | | | | | setExecutorInfo is closer to Report. Distinguish reportType and defaultReportType Make setter a Report member function.
* pkg/report/testdata: update KMSAN reportsTaras Madan2025-06-2023-0/+23
|
* pkg/report: use crash.KMSANTaras Madan2025-06-201-0/+2
| | | | We have crash.KMSAN definition that is not used.
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-14 14:27:53 +0000