It was mentioned a lot during this year's LPC. It's okay if the reproducer runs some common initialization code with privileges first (e.g. to set up networking devices) if that common code is adequate, then drops privileges and runs the fuzzer-generated program. One approach could be to automatical...

https://lore.kernel.org/all/[email protected]/T/#e87cd2d209a9f802a0032bc1b31ebe952da69d85a When sending monthly reports, we could Cc people related to the findings we include in those reports. Currently we only send the reports to mailing lists and sometimes also to maintainers...

Context: #4352 (comment) Currently we fuzz FreeBSD on a syz-ci instance that under FreeBSD itself, which is somewhat tricky to maintain without the expertise in this area. Now that FreeBSD compilation under Linux has become possible, we may consider doing it under the same Docker container we use f...

Context: https://lore.kernel.org/all/[email protected]/T/ Each time a new kernel image is built, the following happens: syz-ci asks dashboard what commits we expect to eventually find in the tree fuzzed by that instance. syz-ci queries last 200k commits and intersects them wit...

syzkaller-fail.txt go1.19.9 2023/11/09 00:27:34 SYZFATAL: executor 1 failed 11 times: executor 1: exit status 67 SYZFAIL: setns(netns) failed (errno 22: Invalid argument) SYZFAIL: child failed (errno 0: Success) loop exited with status 67

Describe the bug At least one test in pkg/build (but possibly in other parts) incorrectly calls t.Fatal()/t.Fatalf() from within a goroutine. Per the documentation (https://pkg.go.dev/testing#T.FailNow), t.FailNow() (which is wrapped by t.Fatal() and t.Fatalf()) shouldn't be called from within a gor...

Context: see discussion at #4232 (comment) Sometimes it's practical to introduce template fields that can either take a specified const value or a range of const values: type template[CLASS, ...] { class flags[CLASS, int8:3] // ... } type singleClassType template[SINGLE_CONST] type subClassType t...

It's quite common for calls in sys/*/tests to rely on default values from descriptions. For example: syzkaller/sys/linux/test/btf_id Line 17 in f757a32 r4 = bpf$BPF_PROG_WITH_BTFID_LOAD(0x5, &AUTO=@bpf_...

Describe the bug In the syzkaller web, when I click on coverage, I get: failed to generate coverage profile: found unexpected tag PartialUnit on top level Expected behavior Coverage is shown If I put continue instead of return in here, it seems to proceed (but is obviously wrong): sy...

Currently we are trying to enforce Cc'ing syzkaller-bugs@ mailing list by reminding users that it's necessary syzkaller/dashboard/app/reporting_email.go Lines 1211 to 1215 in 3cefb14 func warnMailingListInCC...