From: Erkan Erdem <hexvalid@gmail.com>
To: Nathan Chancellor <nathan@kernel.org>, Nicolas Schier <nsc@kernel.org>
Cc: Erkan Erdem <hexvalid@gmail.com>,
Julian Braha <julianbraha@gmail.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] checkkconfigsymbols: resolve revisions before resetting the tree
Date: Sat, 5 Sep 2026 15:32:22 +0300 [thread overview]
Message-ID: <20260905123237.40670-2-hexvalid@gmail.com> (raw)
In-Reply-To: <20260905123237.40670-1-hexvalid@gmail.com>
The commit comparison resets the current branch to commit_a before
resolving commit_b. If the second revision is HEAD or the current branch
name, it then resolves to the first revision. For example, --diff
HEAD^..HEAD compares the parent with itself and silently misses newly
undefined symbols. The same problem affects --commit with the current
branch name.
Resolve and verify both revisions as commits before the first reset.
This keeps their meaning stable throughout the comparison and rejects
invalid endpoints before changing the working tree.
Keep lookup diagnostics separate from the resolved hashes. Use the
resolved range for --find too, since resetting also updates ORIG_HEAD.
Fixes: b1a3f243485f ("checkkconfigsymbols.py: make it Git aware")
Link: https://lore.kernel.org/20210901145212.478066-1-arielmarcovitch@gmail.com/
Assisted-by: LLM
Signed-off-by: Erkan Erdem <hexvalid@gmail.com>
---
An AI coding assistant found the issue, prepared the fix and changelog,
and ran the verification below after a request to find reproducible
functional bugs in Linux development tools.
Validation:
- Ran the actual CLI against disposable Git repositories, comparing the
original script with the patched source. All 15 patched cases pass.
- Covered HEAD-relative ranges, branch names, hashes, tags, annotated
tags, ambiguous branch/tag names, identical revisions, --commit,
--find, ORIG_HEAD and invalid or non-commit endpoints.
- Checked HEAD, current branch, index and tracked file contents after
every invocation. The patched cases preserve these values, including
when the second revision is invalid.
scripts/checkkconfigsymbols.py | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/scripts/checkkconfigsymbols.py b/scripts/checkkconfigsymbols.py
index 36c920e7..e0a1a631 100755
--- a/scripts/checkkconfigsymbols.py
+++ b/scripts/checkkconfigsymbols.py
@@ -150,6 +150,13 @@ def print_undefined_symbols():
undefined_a = {}
undefined_b = {}
+ commit_a = execute(["git", "rev-parse", "--verify", commit_a + "^{commit}"],
+ stderr=None).strip()
+ commit_b = execute(["git", "rev-parse", "--verify", commit_b + "^{commit}"],
+ stderr=None).strip()
+ if args.diff:
+ args.diff = commit_a + ".." + commit_b
+
# get undefined items before the commit
reset(commit_a)
undefined_a, _ = check_symbols(args.ignore)
@@ -223,10 +230,10 @@ def red(string):
return "\033[31m%s\033[0m" % string if COLOR else string
-def execute(cmd):
+def execute(cmd, stderr=subprocess.STDOUT):
"""Execute %cmd and return stdout. Exit in case of error."""
try:
- stdout = subprocess.check_output(cmd, stderr=subprocess.STDOUT, shell=False)
+ stdout = subprocess.check_output(cmd, stderr=stderr, shell=False)
stdout = stdout.decode(errors='replace')
except subprocess.CalledProcessError as fail:
exit(fail)
--
2.50.1 (Apple Git-155)
next prev parent reply other threads:[~2026-09-05 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 12:32 [PATCH 1/2] kconfig: preserve the final answer when input has no newline Erkan Erdem
2026-09-05 12:32 ` Erkan Erdem [this message]
2026-09-05 14:11 ` [PATCH 2/2] checkkconfigsymbols: resolve revisions before resetting the tree Julian Braha
2026-09-05 14:11 ` [PATCH 1/2] kconfig: preserve the final answer when input has no newline Julian Braha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260905123237.40670-2-hexvalid@gmail.com \
--to=hexvalid@gmail.com \
--cc=julianbraha@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®