From: Jason Wang <jasowang@redhat.com>
To: arei.gonglei@huawei.com, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, peter.huangpeng@huawei.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/4] net/socket: fix Uninitialized scalar variable
Date: Thu, 20 Nov 2014 14:22:14 +0800 [thread overview]
Message-ID: <546D8896.2020801@redhat.com> (raw)
In-Reply-To: <1416463034-8264-3-git-send-email-arei.gonglei@huawei.com>
On 11/20/2014 01:57 PM, arei.gonglei@huawei.com wrote:
> From: Gonglei <arei.gonglei@huawei.com>
>
> If is_connected parameter is false, the saddr
> variable will no initialize. Coverity report:
> uninit_use: Using uninitialized value saddr.sin_port.
>
> We don't need add saddr information to nc->info_str
> when is_connected is false.
>
> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
> ---
> net/socket.c | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/net/socket.c b/net/socket.c
> index ca4b8ba..68a93cd 100644
> --- a/net/socket.c
> +++ b/net/socket.c
> @@ -389,11 +389,6 @@ static NetSocketState *net_socket_fd_init_dgram(NetClientState *peer,
>
> nc = qemu_new_net_client(&net_dgram_socket_info, peer, model, name);
>
> - snprintf(nc->info_str, sizeof(nc->info_str),
> - "socket: fd=%d (%s mcast=%s:%d)",
> - fd, is_connected ? "cloned" : "",
> - inet_ntoa(saddr.sin_addr), ntohs(saddr.sin_port));
> -
> s = DO_UPCAST(NetSocketState, nc, nc);
>
> s->fd = fd;
> @@ -404,6 +399,12 @@ static NetSocketState *net_socket_fd_init_dgram(NetClientState *peer,
> /* mcast: save bound address as dst */
> if (is_connected) {
> s->dgram_dst = saddr;
> + snprintf(nc->info_str, sizeof(nc->info_str),
> + "socket: fd=%d (cloned mcast=%s:%d)",
> + fd, inet_ntoa(saddr.sin_addr), ntohs(saddr.sin_port));
> + } else {
> + snprintf(nc->info_str, sizeof(nc->info_str),
> + "socket: fd=%d", fd);
> }
>
> return s;
Reviewed-by: Jason Wang <jasowang@redhat.com>
next prev parent reply other threads:[~2014-11-20 6:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 5:57 [Qemu-devel] [PATCH 0/4] net: fix high impact outstanding defects reported by Coverity arei.gonglei
2014-11-20 5:57 ` [Qemu-devel] [PATCH 1/4] net/slirp: fix memory leak arei.gonglei
2014-11-20 6:20 ` Jason Wang
2014-11-20 11:50 ` Stefan Hajnoczi
2014-11-20 5:57 ` [Qemu-devel] [PATCH 2/4] net/socket: fix Uninitialized scalar variable arei.gonglei
2014-11-20 6:22 ` Jason Wang [this message]
2014-11-20 11:50 ` Stefan Hajnoczi
2014-11-20 5:57 ` [Qemu-devel] [PATCH 3/4] pcnet: fix Negative array index read arei.gonglei
2014-11-20 6:33 ` Jason Wang
2014-11-20 6:36 ` Paolo Bonzini
2014-11-20 6:44 ` Gonglei
2014-11-20 7:08 ` Paolo Bonzini
2014-11-20 7:38 ` Gonglei
2014-11-20 10:03 ` Paolo Bonzini
2014-11-20 5:57 ` [Qemu-devel] [PATCH 4/4] rtl8139: fix Pointer to local outside scope arei.gonglei
2014-11-20 6:29 ` Paolo Bonzini
2014-11-20 6:55 ` Jason Wang
2014-11-20 7:12 ` Gonglei
2014-11-20 7:50 ` Jason Wang
2014-11-20 8:05 ` Gonglei
2014-11-20 8:11 ` Jason Wang
2014-11-20 8:18 ` Gonglei
2014-11-20 8:24 ` Jason Wang
2014-11-20 8:52 ` Gonglei
2014-11-20 9:31 ` Paolo Bonzini
2014-11-20 11:51 ` [Qemu-devel] [PATCH 0/4] net: fix high impact outstanding defects reported by Coverity Stefan Hajnoczi
2014-11-20 11:54 ` Gonglei
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=546D8896.2020801@redhat.com \
--to=jasowang@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=pbonzini@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).