Re: [f2fs-dev] [PATCH V2] libf2fs: Fix using uninitialized variables error in get_device_info()

2023-11-09 Thread Chao Yu
On 2023/11/9 23:47, zangyangyang1 wrote: This issue comes from a static code scanning tool. When c.sparse_mode is 1, stat_buf will not be initialized, but it will be used next. If this issue does not require modification, please ignore this commit. Signed-off-by: zangyangyang1 Reviewed-by:

[f2fs-dev] [PATCH V2] libf2fs: Fix using uninitialized variables error in get_device_info()

2023-11-09 Thread zangyangyang1 via Linux-f2fs-devel
This issue comes from a static code scanning tool. When c.sparse_mode is 1, stat_buf will not be initialized, but it will be used next. If this issue does not require modification, please ignore this commit. Signed-off-by: zangyangyang1 --- Changes since v1: - Use calloc() instead of malloc()

Re: [f2fs-dev] [PATCH V2] libf2fs: Fix using uninitialized variables error in get_device_info()

2023-11-09 Thread zangyangyang1 via Linux-f2fs-devel
I'm very sorry for replying to the wrong email. Please ignore this email and the previous patch email. Thanks, zangyangyang

[f2fs-dev] [PATCH V2] libf2fs: Fix using uninitialized variables error in get_device_info()

2023-11-09 Thread zangyangyang1 via Linux-f2fs-devel
This issue comes from a static code scanning tool. When c.sparse_mode is 1, stat_buf will not be initialized, but it will be used next. If this issue does not require modification, please ignore this commit. Signed-off-by: zangyangyang1 --- Changes since v1: - Use calloc() instead of malloc()