From 0c05c0a258e8ccd78edaad916be5a9d219db1695 Mon Sep 17 00:00:00 2001 From: Pavel Siska Date: Mon, 10 Nov 2025 16:07:53 +0100 Subject: [PATCH] appFs - Initialize fuse_buf struct to avoid use of uninitialized values Previously, m_buffer members were manually set in the constructor, but not all fields were guaranteed to be initialized, leading to valgrind warnings about uninitialized reads inside libfuse. --- src/appFs/appFs.cpp | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/src/appFs/appFs.cpp b/src/appFs/appFs.cpp index 2cfdbc6..c3f9ffc 100644 --- a/src/appFs/appFs.cpp +++ b/src/appFs/appFs.cpp @@ -363,11 +363,7 @@ static void setFuseOperations(struct fuse_operations* fuseOps) class AppFsFuseBuffer { public: - AppFsFuseBuffer() - { - m_buffer.mem = nullptr; - m_buffer.size = 0; - } + AppFsFuseBuffer() = default; ~AppFsFuseBuffer() { @@ -378,7 +374,7 @@ class AppFsFuseBuffer { fuse_buf* getBuffer() { return &m_buffer; } private: - fuse_buf m_buffer; + fuse_buf m_buffer {}; }; static void fuseLoop(struct fuse_session* session)