[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v3] Add missing initialization for g_autofree variables
From: |
Philippe Mathieu-Daudé |
Subject: |
Re: [PATCH v3] Add missing initialization for g_autofree variables |
Date: |
Mon, 15 Mar 2021 11:21:23 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 |
On 3/15/21 11:13 AM, mrezanin@redhat.com wrote:
> From: Miroslav Rezanina <mrezanin@redhat.com>
>
> When declaring g_autofree variable without inicialization, compiler
Typo "initialization"
> will raise "may be used uninitialized in this function" warning due
> to automatic free handling.
>
> This is mentioned in docs/devel/style.rst (quote from section
> "Automatic memory deallocation"):
>
> * Variables declared with g_auto* MUST always be initialized,
> otherwise the cleanup function will use uninitialized stack memory
>
> Add inicialization for these declarations to prevent the warning and
"initialization"
> comply with coding style.
>
> Signed-off-by: Miroslav Rezanina <mrezanin@redhat.com>
>
> ---
> * v3:
> -- allocate in s390_pci_update_dma_avail instead of NULL init
>
> * v2:
> -- Removed fixes in hw/remote/memory.c and hw/remote/proxy.c
> fixed by patch sent by Zenghui Yu (multi-process: Initialize
> variables declared with g_auto*)
> ---
> hw/s390x/s390-pci-vfio.c | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
Maybe "hw/s390x/s390-pci-vfio" prefix in subject?
Otherwise:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>