Dear all,
we looked into improving commit backporting workflows. This specific commit in this series caught our attention, as it states that backporting will not be trivial. The commit message has this part:
Backport hint: this patch will have a trivial conflict applying to v6.6.y, and other trivial conflicts applying to stable kernels < v6.6.
We want to automate backporting commits with a similar property. Therefore, we build a tool git-llm-pick that simplifies the backporting commit. After cherry-picking, we try to automatically detect dependency-commits. In case of failure, we then try to use the patch tool. If this process fails, we then take the rejected patch files, and feed their content with other context and a task description to backport to an LLM. The resulting code modification is then applied. In case validation is passed, a commit is created. The commit message is always extended by a description of the adapted code change, and with which technique a commit was applied.
We made the tool available on github: https://github.com/awslabs/Git_llm_pick/ We currently use LLMs via the AWS Bedrock service, and default to the Nova Pro model. The patch in this series uses the vanilla version of the tool's current output when running git-llm-pick in its virtual test environment:
SKIP_VENV_GLP_TESTING=1 $GLP_PATH/test/test-in-venv.sh \ git-llm-pick \ --validation-command $GLP_PATH/bin/glp-compile-test-changed-kernel-file.sh \ -x f47c834a9131ae64bee3c462f4e610c67b0a000f
Best, Norbert
Amir Goldstein (1): fs: relax assertions on failure to encode file handles
fs/notify/fdinfo.c | 4 +--- fs/overlayfs/copy_up.c | 5 ++--- 2 files changed, 3 insertions(+), 6 deletions(-)