git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] run-command: document use_shell option

From
Jeff King <peff@peff.net>
Date
Jan 22, 2021, 21:03 UTC
Message-ID
<YAs9pTBsdskC8CPN@coredump.intra.peff.net>
In-Reply-To
<YAs2RMT1rEH/2LSp@coredump.intra.peff.net>
On Fri, Jan 22, 2021 at 03:32:04PM -0500, Jeff King wrote:
Show 15 quoted lines
> Yeah, that is exactly right. "use_shell" just means that the command is
> (possibly) run with a shell. Quoting for any extra arguments is handled
> automatically.
> 
> I think you're correct that this was broken from the start in 10ac85c785
> (upload-pack: add object filtering for partial clone, 2017-12-08).
> That's even before the use_shell was added, and then later it was pushed
> into that conditional by 0b6069fe0a (fetch-pack: test support excluding
> large blobs, 2017-12-08). Presumably because the non-hook path would not
> have worked at all, and that was the first time any of it was actually
> tested. ;)
> 
> (I've cc'd authors of those commits as an FYI; I think both were
> relatively new to the project at the time so misunderstanding this
> subtlety of run-command is not too surprising).
While we're thinking about it, let's beef up the documentation a bit.
-- >8 --
Subject: [PATCH] run-command: document use_shell option

It's unclear how run-command's use_shell option should impact the arguments fed to a command. Plausibly it could mean that we glue all of the arguments together into a string to pass to the shell, in which case that opens the question of whether the caller needs to quote them.

But in fact we don't implement it that way (and even if we did, we'd probably auto-quote the arguments as part of the glue step). And we must not receive quoted arguments, because we might actually optimize out the shell entirely (i.e., the caller does not even know if a shell will be involved in the end or not).

Since this ambiguity may have been the cause of a recent bug, let's document the option a bit.

Signed-off-by: Jeff King <peff@peff.net>
---
 run-command.h | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/run-command.h b/run-command.h
index 6472b38bde..d08414a92e 100644
--- a/run-command.h
+++ b/run-command.h
@@ -126,8 +126,15 @@ struct child_process {
 	 */
 	unsigned silent_exec_failure:1;
 
-	unsigned stdout_to_stderr:1;
+	/**
+	 * Run the command from argv[0] using a shell (but note that we may
+	 * still optimize out the shell call if the command contains no
+	 * metacharacters). Note that further arguments to the command in
+	 * argv[1], etc, do not need to be shell-quoted.
+	 */
 	unsigned use_shell:1;
+
+	unsigned stdout_to_stderr:1;
 	unsigned clean_on_exit:1;
 	unsigned wait_after_clean:1;
 	void (*clean_on_exit_handler)(struct child_process *process);
-- 
2.30.0.664.g35e6628185
Previous: Jeff KingNext: Taylor Blau
Message 4 of 13 in “upload-pack.c: fix filter spec quoting bug”
  1. 0/1 upload-pack.c: fix filter spec quoting bugJacob Vosmaer, Jan 22, 2021
  2. 1/1 upload-pack.c: fix filter spec quoting bugJacob Vosmaer, Jan 22, 2021
  3. Jeff KingJan 22, 2021
  4. run-command: document use_shell optionJeff King, Jan 22, 2021
  5. Taylor BlauJan 22, 2021
  6. Junio C HamanoJan 22, 2021
  7. Jeff KingJan 23, 2021
  8. Junio C HamanoJan 22, 2021
  9. upload-pack.c: fix filter spec quoting bugJacob Vosmaer, Jan 25, 2021
  10. Junio C HamanoJan 25, 2021
  11. Jeff KingJan 25, 2021
  12. Jacob VosmaerJan 25, 2021
  13. Jacob VosmaerJan 25, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.