From: Christian Ebner <c.ebner@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Robert Obkircher <r.obkircher@proxmox.com>
Subject: Re: [pbs-devel] [PATCH v2 proxmox-backup 1/2] datastore: check for null pointer when allocating DynamicIndexHeader
Date: Wed, 7 Jan 2026 14:10:12 +0100 [thread overview]
Message-ID: <b4a68c2f-c90d-4d24-bed4-7373242026c3@proxmox.com> (raw)
In-Reply-To: <20251230124154.115442-2-r.obkircher@proxmox.com>
Please provide a short commit message on why this is done.
As far as I see this now panics in handle_alloc_error() if either memory
is exhausted or the layout does not fit the allocator constraints, while
previously this failed on Box::from_raw() for the null pointer?
So maybe better to propagate the allocation error to the call site of
zeroed() in DynamicIndexWriter::create() and return it there as well?
On 12/30/25 1:42 PM, Robert Obkircher wrote:
> Signed-off-by: Robert Obkircher <r.obkircher@proxmox.com>
> ---
> pbs-datastore/src/dynamic_index.rs | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/pbs-datastore/src/dynamic_index.rs b/pbs-datastore/src/dynamic_index.rs
> index ad49cdf3..12df78b1 100644
> --- a/pbs-datastore/src/dynamic_index.rs
> +++ b/pbs-datastore/src/dynamic_index.rs
> @@ -41,13 +41,20 @@ proxmox_lang::static_assert_size!(DynamicIndexHeader, 4096);
> impl DynamicIndexHeader {
> /// Convenience method to allocate a zero-initialized header struct.
> pub fn zeroed() -> Box<Self> {
> + let layout = std::alloc::Layout::new::<Self>();
> unsafe {
> - Box::from_raw(std::alloc::alloc_zeroed(std::alloc::Layout::new::<Self>()) as *mut Self)
> + let ptr = std::alloc::alloc_zeroed(layout) as *mut Self;
> + if ptr.is_null() {
> + std::alloc::handle_alloc_error(layout);
> + }
> + Box::from_raw(ptr)
> }
> }
>
> pub fn as_bytes(&self) -> &[u8] {
> unsafe {
> + // There can't be any uninitialized padding, because the fields
> + // take up all of the statically asserted total size.
> std::slice::from_raw_parts(
> self as *const Self as *const u8,
> std::mem::size_of::<Self>(),
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2026-01-07 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 12:39 [pbs-devel] [PATCH v2 proxmox-backup 0/2] prevent potentially unaligned FixedIndexHeader reference Robert Obkircher
2025-12-30 12:39 ` [pbs-devel] [PATCH v2 proxmox-backup 1/2] datastore: check for null pointer when allocating DynamicIndexHeader Robert Obkircher
2026-01-07 13:10 ` Christian Ebner [this message]
2026-01-07 14:29 ` Robert Obkircher
2026-01-07 14:57 ` Christian Ebner
2025-12-30 12:39 ` [pbs-devel] [PATCH v2 proxmox-backup 2/2] datastore: prevent potentially unaligned FixedIndexHeader reference Robert Obkircher
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=b4a68c2f-c90d-4d24-bed4-7373242026c3@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=r.obkircher@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