From: Robert Obkircher <r.obkircher@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [PATCH v1 proxmox 0/6] uninitialized memory allocations fixes
Date: Tue, 11 Aug 2026 17:01:59 +0200 [thread overview]
Message-ID: <20260811150237.527116-1-r.obkircher@proxmox.com> (raw)
Fix multiple issues around uninitialized allocations and remove unused
buggy code.
All changes are in the proxmox repo. I chose the pbs mailing list
because proxmox-io is mainly used there.
Robert Obkircher (6):
uuid: avoid potential null dereference and memory leaks
io: request zeroed memory instead of manually clearing it
io: avoid potential null dereference and memory leak on error path
io: remove boxed::uninitialized because it is unsound
io: remove unused append_to_vec functions
io: remove unused ByteVecExt trait with grow_ and resize_uninitialized
proxmox-io/src/boxed.rs | 19 +-----
proxmox-io/src/read.rs | 44 ++-----------
proxmox-io/src/vec/byte_vec.rs | 115 ---------------------------------
proxmox-io/src/vec/mod.rs | 37 ++++++-----
proxmox-uuid/src/lib.rs | 14 ++--
5 files changed, 34 insertions(+), 195 deletions(-)
delete mode 100644 proxmox-io/src/vec/byte_vec.rs
--
2.47.3
next reply other threads:[~2026-08-11 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 15:01 Robert Obkircher [this message]
2026-08-11 15:02 ` [PATCH v1 proxmox 1/6] uuid: avoid potential null dereference and memory leaks Robert Obkircher
2026-08-11 15:02 ` [PATCH v1 proxmox 2/6] io: request zeroed memory instead of manually clearing it Robert Obkircher
2026-08-11 15:02 ` [PATCH v1 proxmox 3/6] io: avoid potential null dereference and memory leak on error path Robert Obkircher
2026-08-11 15:02 ` [PATCH v1 proxmox 4/6] io: remove boxed::uninitialized because it is unsound Robert Obkircher
2026-08-11 15:02 ` [PATCH v1 proxmox 5/6] io: remove unused append_to_vec functions Robert Obkircher
2026-08-11 15:02 ` [PATCH v1 proxmox 6/6] io: remove unused ByteVecExt trait with grow_ and resize_uninitialized 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=20260811150237.527116-1-r.obkircher@proxmox.com \
--to=r.obkircher@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