[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZHhOn7QKdByqc3m+@bullseye>
Date: Thu, 1 Jun 2023 07:54:07 +0000
From: Bobby Eshleman <bobbyeshleman@...il.com>
To: Dan Carpenter <dan.carpenter@...aro.org>
Cc: Simon Horman <simon.horman@...igine.com>,
Bobby Eshleman <bobby.eshleman@...edance.com>,
Stefan Hajnoczi <stefanha@...hat.com>,
Stefano Garzarella <sgarzare@...hat.com>,
"Michael S. Tsirkin" <mst@...hat.com>,
Jason Wang <jasowang@...hat.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Wei Liu <wei.liu@...nel.org>, Dexuan Cui <decui@...rosoft.com>,
Bryan Tan <bryantan@...are.com>, Vishnu Dasa <vdasa@...are.com>,
VMware PV-Drivers Reviewers <pv-drivers@...are.com>,
kvm@...r.kernel.org, virtualization@...ts.linux-foundation.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-hyperv@...r.kernel.org
Subject: Re: [PATCH RFC net-next v3 6/8] virtio/vsock: support dgrams
On Wed, May 31, 2023 at 09:13:04PM +0300, Dan Carpenter wrote:
> On Wed, May 31, 2023 at 06:09:11PM +0200, Simon Horman wrote:
> > > @@ -102,6 +144,7 @@ virtio_transport_alloc_skb(struct virtio_vsock_pkt_info *info,
> >
> > Smatch that err may not be initialised in the out label below.
> >
> > Just above this context the following appears:
> >
> > if (info->vsk && !skb_set_owner_sk_safe(skb, sk_vsock(info->vsk))) {
> > WARN_ONCE(1, "failed to allocate skb on vsock socket with sk_refcnt == 0\n");
> > goto out;
> > }
> >
> > So I wonder if in that case err may not be initialised.
> >
>
> Yep, exactly right. I commented out the goto and it silenced the
> warning. I also initialized err to zero at the start hoping that it
> would trigger a different warning but it didn't. :(
>
> regards,
> dan carpenter
>
Thanks for checking that Dan. Fixed in the next rev.
Best,
Bobby
Powered by blists - more mailing lists