From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pbs-devel@lists.proxmox.com, Christian Ebner <c.ebner@proxmox.com>
Subject: [pbs-devel] partially-applied: [PATCH proxmox-backup 0/2] fix possible deadlock for S3 garbage
Date: Thu, 2 Oct 2025 14:15:56 +0200 [thread overview]
Message-ID: <175940724302.1144172.17962215890576494629.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251002091142.222897-1-c.ebner@proxmox.com>
On Thu, 02 Oct 2025 11:11:40 +0200, Christian Ebner wrote:
> The first patch fixes a possible deadlock situation:
> Holding a std::sync::Mutex guard across .await boundaries can lead to
> deadlock situations and must be avoided by all costs. Fix one such
> ocurence when deleting objects from S3 object stores while still
> holding the lock.
>
> The second patch adapts an ill-chosen method name and incorrect
> comment.
>
> [...]
Applied, thanks!
[1/2] datastore: gc: drop mutex lock before entering async context
commit: fa1c2021bbdfc264f1be9e97e5745d9c6a54cd18
skipped the second patch for now, see reply there!
Best regards,
--
Fabian Grünbichler <f.gruenbichler@proxmox.com>
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2025-10-02 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 9:11 [pbs-devel] " Christian Ebner
2025-10-02 9:11 ` [pbs-devel] [PATCH proxmox-backup 1/2] datastore: gc: drop mutex lock before entering async context Christian Ebner
2025-10-02 9:11 ` [pbs-devel] [PATCH proxmox-backup 2/2] datastore: gc: rename method and adapt incorrect comments Christian Ebner
2025-10-02 12:18 ` Fabian Grünbichler
2025-10-02 12:32 ` Christian Ebner
2025-10-02 12:15 ` Fabian Grünbichler [this message]
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=175940724302.1144172.17962215890576494629.b4-ty@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=c.ebner@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.