Open a-nogikh opened 10 months ago
One more cherry-pick to consider is
commit d772781964415c63759572b917e21c4f7ec08d9f
Author: Jakub Kicinski <kuba@kernel.org>
Date: Thu Jan 5 22:33:54 2023 -0800
devlink: bump the instance index directly when iterating
that presumably fixes
commit c2368b19807affd7621f7c4638cd2e17fec13021
Author: Jiri Pirko <jiri@resnulli.us>
Date: Fri Jul 29 09:10:35 2022 +0200
net: devlink: introduce "unregistering" mark and use it during devlinks iteration
But I have a concern that the patch will likely not apply to all intermediate revisions: see this linux-stable discussion.
Our code, at the moment, does not seem to be in position to properly handle cherry-pick conflicts: https://github.com/google/syzkaller/blob/96eb609f6eb9558e2fab491a2c63a11bb0556471/pkg/vcs/linux_patches.go#L52-L55
git cherry-pick
is not atomic, so it can apply some chunks and fail on others. We should either do cherry-pick --abort
on a failure or checkpoint the repository before doing the cherry-pick with some other means, e.g. git stash
.
We cherry-pick some known fixes to make sure that older kernel revisions remain buildable and bootable by our infrastructure during bug bisections.
Thanks to @kaloronahuang for sharing the bigger list of such commits.
We need to fill in some of the
guilty_hash
values and incorporate the list inpkg/vcs
.