All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: mst@redhat.com
Cc: virtualization@lists.linux-foundation.org
Subject: [bug report] virtio_net: rework mergeable buffer handling
Date: Thu, 6 Apr 2017 08:29:49 +0300	[thread overview]
Message-ID: <20170406052949.GA26854@mwanda> (raw)

Hello Michael S. Tsirkin,

The patch 6c8e5f3c41c8: "virtio_net: rework mergeable buffer
handling" from Mar 6, 2017, leads to the following static checker
warning:

	drivers/net/virtio_net.c:1042 virtnet_receive()
	error: uninitialized symbol 'ctx'.

drivers/net/virtio_net.c
  1030  static int virtnet_receive(struct receive_queue *rq, int budget)
  1031  {
  1032          struct virtnet_info *vi = rq->vq->vdev->priv;
  1033          unsigned int len, received = 0, bytes = 0;
  1034          void *buf;
  1035          struct virtnet_stats *stats = this_cpu_ptr(vi->stats);
  1036  
  1037          if (vi->mergeable_rx_bufs) {
  1038                  void *ctx;
                              ^^^
  1039  
  1040                  while (received < budget &&
  1041                         (buf = virtqueue_get_buf_ctx(rq->vq, &len, &ctx))) {
                                                                           ^^^^
  1042                          bytes += receive_buf(vi, rq, buf, len, ctx);
                                                                       ^^^

It's possible that this code is correct, but I looked at it and wasn't
immediately convinced.  Returning non-NULL buf is not sufficient to
show that "ctx" is initialized, because if it's vq->indirect then "buf"
is still unintialized.  Also it's possible that receive_buf() checks
vq->indirect through some side effect way that I didn't see so it
doesn't use the uninitialized value...

I feel like if this is a false positive, that means the rules are too
subtle...  :/

  1043                          received++;
  1044                  }
  1045          } else {
  1046                  while (received < budget &&
  1047                         (buf = virtqueue_get_buf(rq->vq, &len)) != NULL) {
  1048                          bytes += receive_buf(vi, rq, buf, len, NULL);
  1049                          received++;
  1050                  }
  1051          }
  1052  

regards,
dan carpenter

             reply	other threads:[~2017-04-06  5:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06  5:29 Dan Carpenter [this message]
2017-04-06 11:43 ` [bug report] virtio_net: rework mergeable buffer handling Michael S. Tsirkin
2017-06-02 15:35 ` Michael S. Tsirkin

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=20170406052949.GA26854@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    /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.