public inbox for virtualization@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Chaohai Chen <wdhh6@aliyun.com>
Cc: jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
	eperezma@redhat.com, virtualization@lists.linux.dev
Subject: Re: [PATCH v2] virtio_ring: Fix data races in virtqueue_enable_cb_delayed_split()
Date: Wed, 11 Mar 2026 04:01:28 -0400	[thread overview]
Message-ID: <20260311040009-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <54646.126031023201101239@us-mta-438.us.mimecast.lan>

On Wed, Mar 11, 2026 at 11:20:01AM +0800, Chaohai Chen wrote:
> On Fri, Mar 06, 2026 at 05:04:11AM -0500, Michael S. Tsirkin wrote:
> > here's how I would put it:
> > 
> > KCSAN reports .....
> > this is because ....
> > 
> > 
> > This is not a real issue, because ....
> > To disable the KCSAN warning, use READ_ONCE to read vq->split.vring.used->idx.
> > 
> > 
> > 
> > 
> > On Fri, Mar 06, 2026 at 10:24:48AM +0800, Chaohai Chen wrote:
> > > Add READ_ONCE when fetching vq->split.vring.used->idx
> > > without synchronization.
> > 
> > it's with synchronization, of course
> > 
> > > KCSAN detected
> > 
> > detected -> incorrectly reported
> > 
> > > data races when accessing the split virtqueue's
> > > used ring, which is shared memory concurrently accessed by both the CPU
> > > and the virtio device (hypervisor).
> > > 
> > > Example KCSAN report:
> > > 
> > > [  109.277250] ==================================================================
> > > [  109.283600] BUG: KCSAN: data-race in virtqueue_enable_cb_delayed_split+0x10f/0x170
> > > 
> > > [  109.295263] race at unknown origin, with read to 0xffff8b2a92ef2042 of 2 bytes by interrupt on cpu 1:
> > > [  109.306934]  virtqueue_enable_cb_delayed_split+0x10f/0x170
> > > [  109.312880]  virtqueue_enable_cb_delayed+0x3b/0x70
> > > [  109.318852]  start_xmit+0x315/0x860 [virtio_net]
> > > [  109.324532]  dev_hard_start_xmit+0x85/0x380
> > > [  109.329993]  sch_direct_xmit+0xd3/0x680
> > > [  109.335360]  __dev_xmit_skb+0x4ee/0xcc0
> > > [  109.340568]  __dev_queue_xmit+0x560/0xe00
> > > [  109.345701]  ip_finish_output2+0x49a/0x9b0
> > > [  109.350743]  __ip_finish_output+0x131/0x250
> > > [  109.355789]  ip_finish_output+0x28/0x180
> > > [  109.360712]  ip_output+0xa0/0x1c0
> > > [  109.365479]  __ip_queue_xmit+0x68d/0x9e0
> > > [  109.370156]  ip_queue_xmit+0x33/0x40
> > > [  109.374783]  __tcp_transmit_skb+0x1703/0x1970
> > > [  109.379467]  __tcp_send_ack.part.0+0x1bb/0x320
> > > ...
> > > [  109.499585]  do_idle+0x7a/0xe0
> > > [  109.502979]  cpu_startup_entry+0x25/0x30
> > > [  109.506481]  start_secondary+0x116/0x150
> > > [  109.509930]  common_startup_64+0x13e/0x141
> > > 
> > > [  109.516626] value changed: 0x0029 -> 0x002a
> > > ================================================================================
> > > 
> > > Signed-off-by: Chaohai Chen <wdhh6@aliyun.com>
> > 
> > 
> > 
> > I'd like to see code size before/after compared, and included in
> > the log. Does this make the compiler's work much harder?
> > 
> I found the code size is the same. And virtio_store_mb() can do sync.
> Perhaps we don't need to modify the code here, but rather fix KCSAN.


I think your patch is useful, thanks! Just pls tweak the commit log,
including my suggestions and mentioning code size is the same,
repost, and it can go in.

Thanks!


-- 
MST


  parent reply	other threads:[~2026-03-11  8:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06  2:24 [PATCH v2] virtio_ring: Fix data races in virtqueue_enable_cb_delayed_split() Chaohai Chen
2026-03-06 10:04 ` Michael S. Tsirkin
2026-03-11  3:20   ` Chaohai Chen
     [not found]   ` <54646.126031023201101239@us-mta-438.us.mimecast.lan>
2026-03-11  8:01     ` Michael S. Tsirkin [this message]
2026-03-10  8:34 ` 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=20260311040009-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=wdhh6@aliyun.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