From a9f2482fa568fcf1505b249d999dc43251ae5120 Mon Sep 17 00:00:00 2001 From: Bryce Kwon Date: Sat, 17 Oct 2026 17:09:16 -1000 Subject: Isolate git from HOME before git's own setup Git reads the global config for its trace settings before cmd_main is reached, so the isolation there came too late and every request probed $HOME/.gitconfig. The home-access test had passed on arm64 only because access is no syscall of its own there, so it now traces every call that takes a path. --- source/cgit.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'source') diff --git a/source/cgit.c b/source/cgit.c index 6d663fe..5f8ecfa 100644 --- a/source/cgit.c +++ b/source/cgit.c @@ -56,10 +56,12 @@ struct refmatch { /* * Isolate git from the calling user's configuration, which could otherwise - * break once HOME is unset below. Called from cmd_main rather than from a - * constructor attribute, because git-compat-util.h defines __attribute__ - * away on a compiler without it, which would leave this silently unrun. + * break once HOME is unset below. It runs as a constructor because git reads + * the global config for its trace settings before cmd_main is reached, and + * cmd_main calls it again for a compiler that drops the attribute, which + * git-compat-util.h defines away where it is unsupported. */ +__attribute__((constructor)) static void isolate_git_environment(void) { setenv("GIT_CONFIG_NOSYSTEM", "1", 1); -- cgit