aboutsummaryrefslogtreecommitdiffstats
path: root/pkg/report/testdata/openbsd
Commit message (Collapse)AuthorAgeFilesLines
* pkg/report/testdata: regenerateTaras Madan2026-01-091-1/+1
| | | | Update all the test files. I removed test.Equals() check to do it for all the files at once.
* pkg/report: update testdata report typesTaras Madan2025-07-028-0/+8
|
* pkg/report: suppress "Broken pipe" panicsGreg Steuck2022-08-291-0/+4
| | | | They are invalid and we're tired of manually marking them as such.
* pkg/report: use `show panic` output for unscrambled panic messageGreg Steuck2022-08-291-0/+30
| | | | | | The original panic: is printed without logging and is often garbled by concurrent printing by another core. OTOH, `show panic` is printed exclusively so we prefer to use that.
* pkg/report: normalize protection fault report on OpenBSDAnton Lindqvist2021-12-301-0/+304
|
* pkg/report: sync openbsd badop suppressionAnton Lindqvist2021-10-041-5/+5
| | | | This routine was recently renamed.
* pkg/report: do more agressive NUM-replacementAleksandr Nogikh2021-08-133-212/+212
| | | | | | | | | | | | Replace not just long sequences of digits in report titles, but every sequence of '0'-'9' that is not surrounded by word characters. As such matches will overlap and Go does not (currently?) support regexp lookarounds, do the replacement multiple times until there is nothing more to do. This should not slow down syzkaller, since this code is only invoked during crash processing. Restrict LINE replacement only to fragments that have a preceeding file name. This prevents replacements like [1:2] -> [NUM:LINE].
* pkg/report: improve witness reports on OpenBSD (#2468)Anton Lindqvist2021-03-041-0/+287
| | | | | | | | | The witness output was recently changed in order to aid tracking down scenarios in which lock ordering data is missing. This is probably a bug and turning them into unique reports should hopefully help syzkaller being able to find a reproducer. The existing inode suppression must be tweaked a bit order to not flag the relevant reports as suppressed.
* pkg/report: make panic oops on openbsd more stringent (#2315)Anton Lindqvist2020-12-051-0/+24
| | | | | | | | | | | | | It looks we got a couple of odd crashes where the syz-executor is probably hanging but the VM is still responsive[1]. Does the hypervisor try to diagnose the VM under such circumstances? Since the VM is still responsive, the input written to the console is echoed back which in turns causes a panic to be detected. If this theory is true, we can avoid detecting such false positives by making the oops indicator disjoint from the input written to the console. [1] https://syzkaller.appspot.com/bug?id=af604b59c590384e9faa00dfc958ef87a922ae71
* pkg/report: suppress witness vnode lock order reversal on OpenBSDAnton Lindqvist2020-10-272-1/+295
| | | | | | | | | | These reports are not that helpful and are rarely a problem as each vnode has a unique lock. Reports from witness regarding lock order reversal between two vnode locks are already suppressed by the kernel, see RWL_IS_VNODE in the rwlock(9) manual. While here, update `testdata/openbsd/report/10` as this report was generated before I prefixed all output from witness.
* pkg/report: fix uvm_fault report detection on OpenBSDAnton Lindqvist2020-08-061-0/+296
| | | | | | Regression introduced in commit cb93dc6a ("pkg/report: flag short uvm_fault reports as corrupted") causing some valid reports to be flagged as corrupted.
* pkg/report: flag short uvm_fault reports as corruptedAnton Lindqvist2020-07-274-1/+11
| | | | | | | They don't contain enough context to be useful. This change makes `testdata/openbsd/report/0` to be treated as corrupted, which is desirable since it also lacks context.
* pkg/report: make uvm_fault parsing more strict on OpenBSDAnton Lindqvist2020-04-121-0/+2
| | | | | | | | In order to avoid treating the following diagnostic printf as a panic[1]: vmx_mprotect_ept: uvm_fault returns 14, GPA=0x200000 [1] https://syzkaller.appspot.com/bug?id=25f3ef919bf9f5d8a89e13b1ba5fec8ca56334be
* pkg/report: normalize soreceive report on OpenBSDAnton Lindqvist2020-02-272-0/+491
| | | | At last!
* pkg/report: normalize kqueue_check report on OpenBSDAnton Lindqvist2020-01-062-0/+285
|
* pkg/report: normalize unhandled af report on OpenBSDAnton Lindqvist2020-01-031-0/+214
|
* pkg/report: normalize yet another free list modified report on OpenBSDAnton Lindqvist2019-12-091-0/+246
|
* pkg/report: suppress fifo_badop reports on OpenBSDAnton Lindqvist2019-10-261-0/+316
| | | | | This panic is not to interesting since the intended behavior is to panic and it requires root due to usage of mknod(2).
* pkg/report: normalize pool cpu free list modified reports on OpenBSD (#1474)Anton Lindqvist2019-10-221-0/+256
|
* pkg/report: normalize malloc free list modified reports on OpenBSDAnton Lindqvist2019-10-131-0/+227
|
* pkg/report: improve uvm_fault reports on OpenBSDAnton Lindqvist2019-09-281-0/+246
| | | | | | | | Some reports[1] does not include a symbol but rather an address in the "Stopped at" line. There's unfortunately no useful context to add to the title so make them generic instead. [1] https://syzkaller.appspot.com/bug?id=3e44d0b128fd8d6826e4d0044baadcfc02ba7125
* pkg/report: normalize attempt to execute user address reports on OpenBSD (#1431)Anton Lindqvist2019-09-261-0/+303
|
* pkg/report: improve witness extraction for OpenBSDAnton Lindqvist2019-08-301-0/+317
| | | | | | | | | Reports from witness regarding returning to userspace with locks held is not unique enough, causing all lock leaks to be grouped under the same bug. Instead try to extract the name of syscall where the first held lock was grabbed. While here, shorten the title a bit.
* pkg/report: work around GCE console bugsDmitry Vyukov2019-03-291-0/+13
|
* pkg/report: improve page fault detection on OpenBSDAnton Lindqvist2019-03-152-1/+286
| | | | Fixes #1059
* pkg/report: normalize timeout_add panic on OpenBSDAnton Lindqvist2019-02-151-0/+212
|
* openbsd: remove shorten report logic (#986)Anton Lindqvist2019-02-091-8/+4
| | | | | | | | | | | A line length of 79 in the ddb output does not necessarily imply that the following line is a continuation of the current line. Since there's no way to distinguish between ordinary and continuation lines, it could end up corrupting the report by joining two lines that are disjoint[1]. Instead, disable line wrapping in ddb. If we want some kind of wrapping in the future it's easier done by pkg/report. [1] https://syzkaller.appspot.com/bug?extid=03f7377a9848d7d008c9
* pkg/report: improved witness handlingAnton Lindqvist2019-01-282-0/+357
| | | | | | Possible now since the output is consistently prefixed[1]. [1] https://marc.info/?l=openbsd-cvs&m=154850328128727&w=2
* pkg/report: recognize witness on OpenBSDAnton Lindqvist2019-01-241-0/+137
|
* pkg/report: lower uvm_fault oops precedence to favor more specific titlesAnton Lindqvist2018-12-241-0/+24
|
* pkg/report: normalize OpenBSD assertion messagesAnton Lindqvist2018-12-241-0/+115
|
* pkg/report: do not interpret reorder_kernel lines as a crash on OpenBSDAnton Lindqvist2018-11-121-0/+23
| | | | | | Sometimes the reorder_kernel error message is truncated causing the current ignore pattern to fail. Instead, simply reject all lines containing `reorder_kernel' in order to reduce noisy crash reports.
* pkg/report: improve OpenBSD output parsingDmitry Vyukov2018-10-111-0/+121
| | | | | OpenBSD produces \n\r for new lines and split output at 79 column. Handle both of these things.
* Add mandatory OpenBSD bits (#689)Anton Lindqvist2018-08-286-0/+81
all: add openbsd support squash of the following commits: * openbsd: add mandatory bits * report: add OpenBSD support * executor: skip building kvm on OpenBSD * executor: add OpenBSD support Linking against libutil is necessary due to usage of openpty(3). * executor: fix typo in fail() message * fixup! report: add OpenBSD support * fixup! openbsd: add mandatory bits * fixup! openbsd: add mandatory bits * fixup! openbsd: add mandatory bits * fixup! report: add OpenBSD support * gometalinter: skip sys/openbsd
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-12 00:26:28 +0000