public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: "Proxmox Backup Server development discussion"
	<pbs-devel@lists.proxmox.com>,
	"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup v2 0/3] rework GC-related locks
Date: Thu, 2 Oct 2025 11:22:42 +0200	[thread overview]
Message-ID: <0422cd39-7edc-4f52-bc6e-4a547c160afa@proxmox.com> (raw)
In-Reply-To: <20251002072843.88042-1-f.gruenbichler@proxmox.com>

On 10/2/25 9:28 AM, Fabian Grünbichler wrote:
> this series reworks some of the locking behaviour surrounding GC.
> 
> the first patch removes a potentially problematic combination of
> std::sync::Mutex and async S3 code (this should be the last such code
> path), by storing the ProcessLocker guard inside the mutex while holding
> it just for storing/querying/dropping that guard, instead of for the
> duration of GC.
> 
> the second and third patches get rid of racy interactions between
> pre-reload backup sessions and post-reload GC tasks. while this race
> doesn't lead to data loss, it breaks the expected priority of such
> tasks.
> 
> v2: rework first patch to keep locking the Mutex first
> 
> Fabian Grünbichler (3):
>    GC: rework locking logic
>    backup env: keep a shared chunk store lock for duration of backup
>    index writers: remove chunk store lock
> 
>   pbs-datastore/src/datastore.rs     | 527 +++++++++++++++--------------
>   pbs-datastore/src/dynamic_index.rs |   6 +-
>   pbs-datastore/src/fixed_index.rs   |   6 +-
>   src/api2/backup/environment.rs     |   5 +
>   src/api2/backup/mod.rs             |   4 +-
>   5 files changed, 285 insertions(+), 263 deletions(-)
> 

Thanks a lot for your efforts on fixing these issues!

Looks good to me now, consider:

Reviewed-by: Christian Ebner <c.ebner@proxmox.com>


_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel

  parent reply	other threads:[~2025-10-02  9:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02  7:27 Fabian Grünbichler
2025-10-02  7:27 ` [pbs-devel] [PATCH proxmox-backup v2 1/3] GC: rework locking logic Fabian Grünbichler
2025-10-02  7:27 ` [pbs-devel] [PATCH proxmox-backup v2 2/3] backup env: keep a shared chunk store lock for duration of backup Fabian Grünbichler
2025-10-02  7:27 ` [pbs-devel] [PATCH proxmox-backup v2 3/3] index writers: remove chunk store lock Fabian Grünbichler
2025-10-02  9:22 ` Christian Ebner [this message]
2025-10-02 12:10 ` [pbs-devel] applied-series: [PATCH proxmox-backup v2 0/3] rework GC-related locks Fabian Grünbichler

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=0422cd39-7edc-4f52-bc6e-4a547c160afa@proxmox.com \
    --to=c.ebner@proxmox.com \
    --cc=f.gruenbichler@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    /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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal