[google/syzkaller] bf093f: syz-cluster/pkg/triage: move focus and corpus_url ...

[Aleksandr Nogikh]

Branch: refs/heads/gh-readonly-queue/master/pr-7736-c38879ea49099c3d2a402e615172fc71484df058
Home: https://github.com/google/syzkaller
Commit: bf093fd21f8996395348309d927f65ff953a3661
https://github.com/google/syzkaller/commit/bf093fd21f8996395348309d927f65ff953a3661
Author: Aleksandr Nogikh <nog...@google.com>
Date: 2026-08-07 (Fri, 07 Aug 2026)

Changed paths:
M syz-cluster/overlays/gke/prod/global-config.yaml
M syz-cluster/overlays/local/minikube/global-config.yaml
M syz-cluster/pkg/api/api.go
M syz-cluster/pkg/triage/fuzz_target.go

Log Message:
-----------
syz-cluster/pkg/triage: move focus and corpus_url to target level

Subsystem focus area and base corpus URL depend on the mailing list target
rather than individual fuzzing campaigns. Previously, focus and corpus_url
were duplicated across every campaign within a target.

Move focus and corpus_url from KernelFuzzConfig to FuzzTriageTarget in API
definitions and update campaign expansion so campaigns inherit these values
from their parent target when not explicitly specified. This simplifies overlay
configurations and prepares for multi-track campaigns sharing the same corpus
and focus area.


Commit: 8c29bef592f9090630c88a873e6b2b96c3477b19
https://github.com/google/syzkaller/commit/8c29bef592f9090630c88a873e6b2b96c3477b19
Author: Aleksandr Nogikh <nog...@google.com>
Date: 2026-08-07 (Fri, 07 Aug 2026)

Changed paths:
M pkg/aflow/ai/ai.go
M pkg/aflow/flow/fuzzing/patch_triage.go

Log Message:
-----------
pkg/aflow/flow/fuzzing: add conditional kmsan triage sub-agent

KMSAN fuzzing sessions incur substantial resource overhead compared to standard
fuzzing. Moreover, standard KASAN kernel configurations already detect
out-of-bounds accesses, use-after-free errors, and locking bugs via LOCKDEP.

Add a conditional kmsan-evaluator sub-agent to the patch-triage workflow that
executes via aflow.If only when WorthFuzzing is true. The sub-agent evaluates
whether code changes introduce or modify uninitialized memory risks or
kernel-to-user memory info-leaks detectable exclusively by KMSAN, populating
NeedsKMSAN in the triage result.


Commit: e4ef95d66b43846d6ffc71464fef148e16493289
https://github.com/google/syzkaller/commit/e4ef95d66b43846d6ffc71464fef148e16493289
Author: Aleksandr Nogikh <nog...@google.com>
Date: 2026-08-07 (Fri, 07 Aug 2026)

Changed paths:
M syz-cluster/overlays/gke/prod/global-config.yaml
M syz-cluster/overlays/gke/staging/global-config.yaml
M syz-cluster/overlays/local/minikube/global-config.yaml
M syz-cluster/pkg/api/api.go
M syz-cluster/pkg/app/config.go
M syz-cluster/pkg/triage/ai.go
M syz-cluster/workflow/triage/main.go

Log Message:
-----------
syz-cluster/workflow/triage: gate kmsan fuzzing targets on ai verdict

To prevent unnecessary resource consumption on KMSAN fuzzing runs, integrate
the AI KMSAN triage verdict into syz-cluster workflow execution.

Define track type constants for KASAN and KMSAN. In prepareFuzzingTask, when a
target belongs to the KMSAN track, check whether the AI triage verdict indicated
NeedsKMSAN. If not, skip the KMSAN test target with a descriptive triage skip
reason. Add KMSAN campaigns to network target configurations in overlays.


Compare: https://github.com/google/syzkaller/compare/bf093fd21f89%5E...e4ef95d66b43

To unsubscribe from these emails, change your notification settings at https://github.com/google/syzkaller/settings/notifications

[Aleksandr Nogikh]

Branch: refs/heads/master

Compare: https://github.com/google/syzkaller/compare/c38879ea4909...e4ef95d66b43