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

Re: [PATCH v2 3/4] reftable/stack: move list lock to `struct reftable_stack`

From
Patrick Steinhardt <ps@pks.im>
Date
Aug 25, 2026, 10:30 UTC
Message-ID
<ao1uqpCxFHlOyTV-@pks.im>
In-Reply-To
<20260824-740-optimize-reloading-the-reftable-stack-v2-3-9c9de2eb0af7@gmail.com>
On Mon, Aug 24, 2026 at 11:31:01AM +0200, Karthik Nayak wrote:
Show 22 quoted lines
> diff --git a/reftable/stack.c b/reftable/stack.c
> index 703548417c..c3d4deff29 100644
> --- a/reftable/stack.c
> +++ b/reftable/stack.c
> @@ -628,10 +630,16 @@ int reftable_stack_reload(struct reftable_stack *st)
>  }
>  
>  struct reftable_addition {
> -	struct reftable_flock tables_list_lock;
>  	struct reftable_stack *stack;
>  	struct reftable_write_options opts;
>  
> +	/*
> +	 * While the list lock is acquired on the stack, we need to distinguish
> +	 * which 'reftable_addition' is responsible for the lock. This avoids
> +	 * clearing the lock of another 'reftable_addition'.
> +	 */
> +	unsigned int locked : 1;
> +
>  	char **new_tables;
>  	size_t new_tables_len, new_tables_cap;
>  	uint64_t next_update_index;

This feels somewhat fragile, as tracking state via a bit is very easy to get wrong. I would have preferred a solution where we didn't have to have this field and instead a more direct proxy. But there's not that many spots where we have to do this, so this may be okay-ish.

Other than that this series looks good to me, thanks!
Patrick
Previous: Karthik NayakNext: Karthik Nayak
Message 5 of 9 in “reftable/stack: avoid reloading the stack when locked”
  1. 0/4 reftable/stack: avoid reloading the stack when lockedKarthik Nayak, Aug 24, 2026
  2. 1/4 reftable/stack: remove `REFTABLE_STACK_NEW_ADDITION_RELOAD`Karthik Nayak, Aug 24, 2026
  3. 2/4 reftable/stack: rename reftable_stack_new_addition()Karthik Nayak, Aug 24, 2026
  4. 3/4 reftable/stack: move list lock to `struct reftable_stack`Karthik Nayak, Aug 24, 2026
  5. Patrick SteinhardtAug 25, 2026
  6. Karthik NayakAug 26, 2026
  7. 4/4 reftable/stack: avoid reloading the stack when already lockedKarthik Nayak, Aug 24, 2026
  8. Jeff KingAug 24, 2026
  9. Karthik NayakAug 26, 2026

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.