From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pbs-devel@lists.proxmox.com, Christian Ebner <c.ebner@proxmox.com>
Subject: applied: [PATCH proxmox-backup] pbs-key-config: align fsync behavior when storing new/existing key
Date: Thu, 16 Apr 2026 15:42:30 +0200 [thread overview]
Message-ID: <177634694101.663260.5103535490301918294.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260324100413.215443-1-c.ebner@proxmox.com>
On Tue, 24 Mar 2026 11:04:13 +0100, Christian Ebner wrote:
> In case a key is stored by replacing the file contents, the file
> contents are synced to disk as the corresponding flag is set for
> proxmox-sys::fs::replace_file(). When creating a new file however,
> fsync is never called.
>
> Align the behaviour by also calling fsync in case of storing the key
> to a new file.
>
> [...]
Applied, thanks!
[1/1] pbs-key-config: align fsync behavior when storing new/existing key
commit: 322ca18a4039fb92f0c99f2665e2a51272fa4e31
Best regards,
--
Fabian Grünbichler <f.gruenbichler@proxmox.com>
prev parent reply other threads:[~2026-04-16 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 10:04 Christian Ebner
2026-03-24 13:17 ` Fabian Grünbichler
2026-03-24 13:30 ` Christian Ebner
2026-04-16 13:42 ` 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=177634694101.663260.5103535490301918294.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox