All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@redhat.com>
To: Sun Ke <sunke32@huawei.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] src/swapon.c: initiate p to NULL
Date: Sat, 30 Jan 2021 12:58:18 +0800	[thread overview]
Message-ID: <20210130045817.GV14354@localhost.localdomain> (raw)
In-Reply-To: <20210128065010.218830-1-sunke32@huawei.com>

On Thu, Jan 28, 2021 at 02:50:10PM +0800, Sun Ke wrote:
> when run make, show:
> swapon.c:135:3: warning: 'p' may be used uninitialized in this function
> [-Wmaybe-uninitialized]
>    memcpy(p, buf, BUF_SIZE);
>       ^~~~~~~~~~~~~~~~~~~~~~~~
> fix it.

If you don't have a situation to prove this's a real bug, I guess the gcc might
think the 'p' can be used uninitialized at here when verb is TEST_MWRITE_BEFORE_AND_MWRITE_AFTER:

        case TEST_MWRITE_BEFORE_AND_MWRITE_AFTER:
                memcpy(p, buf, BUF_SIZE);
                break;

But from the code logic, if verb is TEST_MWRITE_BEFORE_AND_MWRITE_AFTER, the 'p'
will be initialized by:

        switch (verb) {
        case TEST_MWRITE_BEFORE_AND_MWRITE_AFTER:
        case TEST_MWRITE_BEFORE:
                p = mmap(NULL, BUF_SIZE, PROT_WRITE | PROT_READ, MAP_SHARED,


So I think this's a fake uninitialized warning (Maybe I'm wrong. But if I'm right,
better to specify that in commit log).

Anyway, I personally don't object to initialize a pointer to NULL at beginning,
and make a build warning disappear. Leave the decision to maintainer :)


Thanks,
Zorro

> 
> Signed-off-by: Sun Ke <sunke32@huawei.com>
> ---
>  src/swapon.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/src/swapon.c b/src/swapon.c
> index afaed405..fe8949a3 100644
> --- a/src/swapon.c
> +++ b/src/swapon.c
> @@ -41,7 +41,7 @@ int main(int argc, char **argv)
>  		.sa_handler	= handle_signal,
>  	};
>  	enum verbs verb = TEST_SWAPON;
> -	void *p;
> +	void *p = NULL;
>  	ssize_t sz;
>  	int fd = -1;
>  	int ret, c;
> -- 
> 2.13.6
> 


  reply	other threads:[~2021-01-30  9:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28  6:50 [PATCH] src/swapon.c: initiate p to NULL Sun Ke
2021-01-30  4:58 ` Zorro Lang [this message]
2021-02-01  3:18   ` sunke (E)

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=20210130045817.GV14354@localhost.localdomain \
    --to=zlang@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=sunke32@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.