github.com-google-syzkaller

all: apply modernize linter

all/mocks: update

all: use any instead of interface{} Any is the preferred over interface{} now in Go.

all: trivial for-loop range refactorings Fixes for "Use range over integer instead of traditional for loop" linter warnings that boil down to mechanical replacement. In certain cases untyped constants like 2e5 are converted to integer literals, because they are considered as floats and can't be used in range expressions

dashboard/app: fix API access checks Currently we permit per-namespace clients to access global APIs. For example, a secondary OS syz-manager client can poll bugs from all namespaces. This is wrong and bad. Don't permit namespace clients to access global APIs.

pkg/aflow: abstract LLM provider Decouple the aflow package from the google.golang.org/genai library to enable future integration with other LLM providers (e.g., Claude). Introduce a generic backend.Provider interface and corresponding types (Message, Part, GenerateConfig, etc.) in pkg/aflow/backend. Move the existing Gemini-specific logic into pkg/aflow/backend/gemini, which now implements this interface. Update the core aflow execution logic and agents to rely solely on the generic backend types. Finally, update syz-agent and tools/syz-aflow to explicitly initialize the Gemini provider and inject it into the workflow execution.

pkg/aflow: add package for agentic workflows

syz-cluster: report session results Provide an API to set up the reporting of finished sessions for which syz-cluster collected reportable findings. The actual sending of the results is to be done in a separate component that would: 1) Call Next() to get the next report to send. 2) Call Confirm() to confirm that the report has been sent. 3) Call Upstream() if the report has been moderated and needs to be sent to e.g. public mailing lists.

dashboard/config/linux: add upstream-rust-kasan config Enable RUST as well as other Rust-related configs.

dashboard/app: add support for AI workflows Support for: - polling for AI jobs - handling completion of AI jobs - submitting job trajectory logs - basic visualization for AI jobs

dashboard/config/linux: disable CONFIG_CGROUP_BPF It seems incredibly difficult to clean up the side effects of this kernel functionality. Keep it enabled only on a new config dedicated specifically for the snapshot-based instance. Closes #5956.

dashboard/app: react to user comments under AI patches Implement all basic fucntionality of running iteration workflow on new comments and submitting new versions of patches / comment replies. Once in a while, the system will now schedule a patch iteration workflow to react to new user comments. Depending on the result, it will either submit a new version of the series or send an aggregated reply email. New comments on previous versions are for now ignored.

executor: update flatbuffers Update flatbuffers to v23.5.26, which matches the compiler version in the new env container.

pkg/spanner: unify Spanner client abstraction and switch to emulator-based testing - Refactored pkg/coveragedb, pkg/cover/heatmap, syz-cluster, and dashboard/app to use concrete *spanner.Client instead of mockable interface proxy. - Moved Spanner Emulator control code, ParseURI, and database setup to a shared library utility in pkg/spanner/emulator.go. - Replaced mock-based testing with Spanner Emulator-based testing across all test cases. - Removed deprecated interfaces from pkg/spanner and deleted the spannerclient/ proxy layer and its mocks.

dashboard/app, pkg/dungeon: implement syzkaller dungeon gamification Introduce the Syzkaller Dungeon, a gamified leaderboard ranking kernel contributors based on their bug-fixing activity. The patch includes: - Backend logic to fetch bug entities from Datastore, compute player XP/levels via deterministic heuristics, map domain emails to corporate Kingdoms, and assign RPG classes based on subsystem tags. - Three new HTTP endpoints (/syz-dungeon, /syz-dungeon/hero, and /syz-dungeon/kingdom) with programmatic JSON support. - Fully interactive frontend HTML templates and styling emphasizing a retro dark-mode aesthetic.

pkg/manager: split off diff fuzzer functionality Move the code to a separate pkg/manager/diff package. Split the code into several files.

dashboard/app: introduce AI job reporting API The API will let us implement external AI job reporters. Several configurable stages are supported.

pkg/codesearch: add skeleton for code searching tool Add a clang tool that is used for code indexing (tools/clang/codesearch/). It follows conventions and build procedure of the declextract tool. Add pkg/codesearch package that aggregates the info exposed by the clang tools, and allows doing simple queries: - show source code of an entity (function, struct, etc) - show entity comment - show all entities defined in a source file Add tools/syz-codesearch wrapper tool that allows to create index for a kernel build, and then run code queries on it.

dashboard/app: show manager unique coverage 1. Make heatmap testable, move out the spanner client instantiation. 2. Generate spannerdb.ReadOnlyTransaction mocks. 3. Generate spannerdb.RowIterator mocks. 4. Generate spannerdb.Row mocks. 5. Prepare spannerdb fixture. 6. Fixed html control name + value. 7. Added multiple tests. 8. Show line coverage from selected manager. 9. Propagate coverage url params to file coverage url.

prog: generate choice table only for enabled calls We used to generate a choice table and do its normalization for all present syscalls, also it was not considered during the /prio page generation. Enabled/disabled syscalls were accounted for in the choice table construction, but there's a chance that the resulting table was still somewhat skewed. The situation must have become worse after several thousands of auto syscalls were added.