Re: [PATCH][ocfs2-next] ocfs2: ensure ret is set to zero before returning
From: Joseph Qi
Date: Wed Aug 07 2019 - 08:35:41 EST
On 19/8/7 20:19, Colin King wrote:
> From: Colin Ian King <colin.king@xxxxxxxxxxxxx>
>
> A previous commit introduced a regression where variable ret was
> originally being set from the return from a call to function
> dlm_create_debugfs_subroot and this set was removed. Currently
> ret is now uninitialized if no alloction errors are found which
> may end up with a bogus check on ret < 0 on the 'leave:' return
> path. Fix this by setting ret to zero on a successful execution
> path.
Good catch.
Or shall we just initialize 'ret' at first?
>
> Addresses-Coverity: ("Uninitialzed scalar variable")
Typo here.
Thanks,
Joseph
> Fixes: cba322160ef0 ("ocfs2: further debugfs cleanups")
> Signed-off-by: Colin Ian King <colin.king@xxxxxxxxxxxxx>
> ---
> fs/ocfs2/dlm/dlmdomain.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/ocfs2/dlm/dlmdomain.c b/fs/ocfs2/dlm/dlmdomain.c
> index 5c4218d66dd2..ee6f459f9770 100644
> --- a/fs/ocfs2/dlm/dlmdomain.c
> +++ b/fs/ocfs2/dlm/dlmdomain.c
> @@ -2052,6 +2052,7 @@ static struct dlm_ctxt *dlm_alloc_ctxt(const char *domain,
> mlog(0, "context init: refcount %u\n",
> kref_read(&dlm->dlm_refs));
>
> + ret = 0;
> leave:
> if (ret < 0 && dlm) {
> if (dlm->master_hash)
>