From d922ca7efda29b23dfb85abe37aee1641c4fbe05 Mon Sep 17 00:00:00 2001
From: Aleksandr Nogikh <nogikh@google.com>
Date: Wed, 19 Jul 2023 14:14:10 +0200
Subject: syz-ci: specify per-manager bisection backports

It might be the case that the kernels that are being fuzzed on syz-ci
require their own backports to build/test older revisions during
bisection.

Let users specify it in the syz-ci config.
---
 pkg/vcs/linux.go | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'pkg/vcs/linux.go')

diff --git a/pkg/vcs/linux.go b/pkg/vcs/linux.go
index 16e1c79fa..589c300b8 100644
--- a/pkg/vcs/linux.go
+++ b/pkg/vcs/linux.go
@@ -139,6 +139,7 @@ func gitReleaseTagToInt(tag string, includeRC bool) uint64 {
 
 func (ctx *linux) EnvForCommit(
 	defaultCompiler, compilerType, binDir, commit string, kernelConfig []byte,
+	backports []BackportCommit,
 ) (*BisectEnv, error) {
 	tagList, err := ctx.previousReleaseTags(commit, true, false, false)
 	if err != nil {
@@ -167,7 +168,7 @@ func (ctx *linux) EnvForCommit(
 		Compiler:     compiler,
 		KernelConfig: cf.Serialize(),
 	}
-	err = linuxFixBackports(ctx.git)
+	err = linuxFixBackports(ctx.git, backports...)
 	if err != nil {
 		return nil, fmt.Errorf("failed to cherry pick fixes: %w", err)
 	}
-- 
cgit mrf-deployment