Dmitry Vyukov
Dmitry Vyukov
Another idea by Ido: https://groups.google.com/d/msg/syzkaller-bugs/79fgOLAX5co/kZnbgbG5BQAJ is to use tags to mark incorrect bisection and then show it on the bug page. Tags could also capture reason for incorrect bisection.
FTR, Debian bug tracker is fully-email-based full-fledged bug tracking system: https://www.debian.org/Bugs/ We could look at features for inspiration of what may be useful, and maybe reuse some actual command syntax...
Another data point: NetBSD people want ``` Consistency and relevance of the "fixed bugs" history, so that we can get a clear view of the most common types of bugs...
+ @tarasmadan
Another bug with __builtin_memcpy/set_inline I hit: #57048
We don't seem to re-exec in Go mode at all: https://github.com/llvm/llvm-project/blob/539fa1df4634dad7d99e4485e4fc3a82ff1a5481/compiler-rt/lib/tsan/rtl/tsan_platform_linux.cpp#L267-L315 Does it still reproduce with the latest release?
pkg/report: syzkaller did not recognise the `not syncing: panic_on_warn set ...` report as corrupted
These are not put into "corrupted report" bucket because they have reproducers. The idea was that we don't want to lose reproducers and it still may be actionable. But I...
pkg/report: syzkaller did not recognise the `not syncing: panic_on_warn set ...` report as corrupted
Another bug where KFENCE report is truncated: https://syzkaller.appspot.com/bug?extid=ca31fd785c3041f508e4
pkg/report: syzkaller did not recognise the `not syncing: panic_on_warn set ...` report as corrupted
We save up to 3MB of output (or something similar). And in either case we should preserve the bug title line (if it would be in the output). I think...
> > Otherwise looks good. We want to deploy this on syzbot, right? > > Yes please. @a-nogikh please add syzbot configs for this