The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Colin King (gmail)" <colin.i.king@gmail.com>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: Jason Wang <jasowang@redhat.com>, Paolo Abeni <pabeni@redhat.com>,
	"Michael S. Tsirkin\"" <mst@redhat.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: re: virtio_net: support device stats
Date: Mon, 14 Oct 2024 10:39:26 +0100	[thread overview]
Message-ID: <eb09900a-8443-4260-9b66-5431a85ca102@gmail.com> (raw)

Hi,

Static analysis on Linux-next has detected a potential issue with the 
following commit:

commit 941168f8b40e50518a3bc6ce770a7062a5d99230
Author: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Date:   Fri Apr 26 11:39:24 2024 +0800

     virtio_net: support device stats


The issue is in function virtnet_stats_ctx_init, in 
drivers/net/virtio_net.c as follows:

         if (vi->device_stats_cap & VIRTIO_NET_STATS_TYPE_CVQ) {
                 queue_type = VIRTNET_Q_TYPE_CQ;

                 ctx->bitmap[queue_type]   |= VIRTIO_NET_STATS_TYPE_CVQ;
                 ctx->desc_num[queue_type] += 
ARRAY_SIZE(virtnet_stats_cvq_desc);
                 ctx->size[queue_type]     += sizeof(struct 
virtio_net_stats_cvq);
         }


ctx->bitmap is declared as a u32 however it is being bit-wise or'd with 
VIRTIO_NET_STATS_TYPE_CVQ and this is defined as 1 << 32:

include/uapi/linux/virtio_net.h:#define VIRTIO_NET_STATS_TYPE_CVQ 
(1ULL << 32)

..and hence the bit-wise or operation won't set any bits in ctx->bitmap 
because 1ULL < 32 is too wide for a u32. I suspect ctx->bitmap should be 
declared as u64.

Colin





             reply	other threads:[~2024-10-14  9:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14  9:39 Colin King (gmail) [this message]
2024-10-14  9:47 ` virtio_net: support device stats Michael S. Tsirkin
2024-10-14 10:14   ` Colin King (gmail)
2024-10-18  7:25     ` Jason Wang
2024-10-15  9:55   ` Xuan Zhuo

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=eb09900a-8443-4260-9b66-5431a85ca102@gmail.com \
    --to=colin.i.king@gmail.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=xuanzhuo@linux.alibaba.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