aboutsummaryrefslogtreecommitdiffstats
path: root/pkg/manager/crash.go
Commit message (Collapse)AuthorAgeFilesLines
* pkg/osutil: fix CreationTimeDmitry Vyukov2026-01-091-3/+1
| | | | | | | | | | We return Ctime from CreationTime. But "C" does not stand for "creation", it stands for "status change" (inode update). It may or may not be the creation time. Use Btime (birth time) for creation time. Fixes #6547
* pkg/manager: add Rank column with tooltips to the main pageTaras Madan2025-08-281-0/+12
|
* pkg/manager: store titles stat in the crash dirTaras Madan2025-08-281-0/+3
|
* pkg/manager: store tail reportsTaras Madan2025-08-281-1/+3
| | | | Send only the first report to dashboard.
* pkg/manager: show bug first timeDmitry Vyukov2025-01-171-0/+2
| | | | | This allows to understand if a bug is new (found in the current run) or old.
* prog: annotate image assets with fsck logsFlorent Revest2024-12-091-1/+1
| | | | | | | | | | | | | | | | | | Syscall attributes are extended with a fsck command field which lets file system mount definitions specify a fsck-like command to run. This is required because all file systems have a custom fsck command invokation style. When uploading a compressed image asset to the dashboard, syz-manager also runs the fsck command and logs its output over the dashapi. The dashboard logs these fsck logs into the database. This has been requested by fs maintainer Ted Tso who would like to quickly understand whether a filesystem is corrupted or not before looking at a reproducer in more details. Ultimately, this could be used as an early triage sign to determine whether a bug is obviously critical.
* tools: add a syz-diff toolAleksandr Nogikh2024-10-251-2/+2
| | | | | | | | | | | | | | This is the prototype version of the patch series fuzzing functionality based on the syzkaller fuzzing engine. The tool takes two syzkaller configs -- one for the base kernel, one for the patched kernel. Optionally the patch itself can be also provided. syz-diff will consider a bug patched-only if: 1) It happened while fuzzing the patched kernel. 2) It was never observed on the base kernel. 3) The tool found a repro on the patched kernel. 4) The repro did not crash the base kernel.
* pkg/manager: tolerate more bug list querying errorsAleksandr Nogikh2024-10-241-1/+9
| | | | | We do not save atomically, so it may happen that there will be some inconsistencies. Just skip those crashes and print a log message.
* pkg/manager: improve error reportingAleksandr Nogikh2024-10-221-1/+1
| | | | If bug info parsing failed, print more details about the problem.
* pkg/manager: tolerate empty crash directoryAleksandr Nogikh2024-10-221-0/+4
| | | | It's okay if there have been no crashes yet.
* pkg/manager: factor out the crash storage functionalityAleksandr Nogikh2024-10-111-0/+304
It reduces the size of the syz-manager/ code and makes it testable. Use it in syz-testbed.