All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: "Johannes Thumshirn" <johannes.thumshirn@wdc.com>,
	"Alexander Graf" <graf@amazon.com>,
	"Jason Wang" <jasowang@redhat.com>,
	"Eugenio Pérez" <eperezma@redhat.com>,
	"open list:VIRTIO CORE" <virtualization@lists.linux.dev>,
	"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] virtio_ring: Add READ_ONCE annotations for device-writable fields
Date: Tue, 3 Feb 2026 07:02:23 -0500	[thread overview]
Message-ID: <20260203065312-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1770107244.8746088-1-xuanzhuo@linux.alibaba.com>

On Tue, Feb 03, 2026 at 04:27:24PM +0800, Xuan Zhuo wrote:
> On Sat, 31 Jan 2026 11:28:09 +0100, Johannes Thumshirn <johannes.thumshirn@wdc.com> wrote:
> > From: Alexander Graf <graf@amazon.com>
> >
> > KCSAN reports data races when accessing virtio ring fields that are
> > concurrently written by the device (host). These are legitimate
> > concurrent accesses where the CPU reads fields that the device updates
> > via DMA-like mechanisms.
> >
> > Add accessor functions that use READ_ONCE() to properly annotate these
> > device-writable fields and prevent compiler optimizations that could in
> > theory break the code. This also serves as documentation showing which
> > fields are shared with the device.
> >
> > The affected fields are:
> > - Split ring: used->idx, used->ring[].id, used->ring[].len
> > - Packed ring: desc[].flags, desc[].id, desc[].len
> >
> > This patch was partially written using the help of Kiro, an
> > AI coding assistant, to automate the mechanical work of generating the
> > inline function definition.
> >
> > Signed-off-by: Alexander Graf <graf@amazon.com>
> > [jth: Add READ_ONCE in virtqueue_kick_prepare_split ]
> > Co-developed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> > Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> > Reviewed-by: Alexander Graf <graf@amazon.com>
> > ---
> > Changes to v2:
> > - Add AI statement (agraf)
> > - Add R-b from agraf
> > - Update comment (mst)
> > - Add split to function names handling split rings (mst)
> > - Add vring_read_split_avail_event() (mst)
> >
> > Changes to v1:
> > - Updated comments (mst, agraf)
> > - Moved _read suffix to prefix in newly introduced functions (mst)
> > - Update my minor contribution to Co-developed-by (agraf)
> > - Add "in theory" to changelog
> > ---
> >  drivers/virtio/virtio_ring.c | 72 +++++++++++++++++++++++++++++-------
> >  1 file changed, 58 insertions(+), 14 deletions(-)
> >
> > diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
> > index ddab68959671..53d5334576bc 100644
> > --- a/drivers/virtio/virtio_ring.c
> > +++ b/drivers/virtio/virtio_ring.c
> > @@ -222,6 +222,55 @@ struct vring_virtqueue {
> >  #endif
> >  };
> >
> > +/*
> > + * Accessors for device-writable fields in virtio rings.
> > + * These fields are concurrently written by the device and read by the driver.
> > + * Use READ_ONCE() to prevent compiler optimizations, document the
> > + * intentional data race and prevent KCSAN warnings.
> > + */
> > +static inline u16 vring_read_split_used_idx(const struct vring_virtqueue *vq)
> 
> "inline" is not recommended in *.c files.

why would it be? it's a compiler hint. given this is the hottest path,
it makes sense.


> Ohters LGTM.
> 
> Thanks.




> 
> > +{
> > +	return virtio16_to_cpu(vq->vq.vdev,
> > +			       READ_ONCE(vq->split.vring.used->idx));
> > +}
> > +
> > +static inline u32 vring_read_split_used_id(const struct vring_virtqueue *vq,
> > +					   u16 idx)
> > +{
> > +	return virtio32_to_cpu(vq->vq.vdev,
> > +			       READ_ONCE(vq->split.vring.used->ring[idx].id));
> > +}
> > +
> > +static inline u32 vring_read_split_used_len(const struct vring_virtqueue *vq, u16 idx)
> > +{
> > +	return virtio32_to_cpu(vq->vq.vdev,
> > +			       READ_ONCE(vq->split.vring.used->ring[idx].len));
> > +}
> > +
> > +static inline u16 vring_read_split_avail_event(const struct vring_virtqueue *vq)
> > +{
> > +	return virtio16_to_cpu(vq->vq.vdev,
> > +			       READ_ONCE(vring_avail_event(&vq->split.vring)));
> > +}
> > +
> > +static inline u16 vring_read_packed_desc_flags(const struct vring_virtqueue *vq,
> > +					       u16 idx)
> > +{
> > +	return le16_to_cpu(READ_ONCE(vq->packed.vring.desc[idx].flags));
> > +}
> > +
> > +static inline u16 vring_read_packed_desc_id(const struct vring_virtqueue *vq,
> > +				            u16 idx)
> > +{
> > +	return le16_to_cpu(READ_ONCE(vq->packed.vring.desc[idx].id));
> > +}
> > +
> > +static inline u32 vring_read_packed_desc_len(const struct vring_virtqueue *vq,
> > +				             u16 idx)
> > +{
> > +	return le32_to_cpu(READ_ONCE(vq->packed.vring.desc[idx].len));
> > +}
> > +
> >  static struct vring_desc_extra *vring_alloc_desc_extra(unsigned int num);
> >  static void vring_free(struct virtqueue *_vq);
> >
> > @@ -736,8 +785,7 @@ static bool virtqueue_kick_prepare_split(struct virtqueue *_vq)
> >  	LAST_ADD_TIME_INVALID(vq);
> >
> >  	if (vq->event) {
> > -		needs_kick = vring_need_event(virtio16_to_cpu(_vq->vdev,
> > -					vring_avail_event(&vq->split.vring)),
> > +		needs_kick = vring_need_event(vring_read_split_avail_event(vq),
> >  					      new, old);
> >  	} else {
> >  		needs_kick = !(vq->split.vring.used->flags &
> > @@ -808,8 +856,7 @@ static void detach_buf_split(struct vring_virtqueue *vq, unsigned int head,
> >
> >  static bool more_used_split(const struct vring_virtqueue *vq)
> >  {
> > -	return vq->last_used_idx != virtio16_to_cpu(vq->vq.vdev,
> > -			vq->split.vring.used->idx);
> > +	return vq->last_used_idx != vring_read_split_used_idx(vq);
> >  }
> >
> >  static void *virtqueue_get_buf_ctx_split(struct virtqueue *_vq,
> > @@ -838,10 +885,8 @@ static void *virtqueue_get_buf_ctx_split(struct virtqueue *_vq,
> >  	virtio_rmb(vq->weak_barriers);
> >
> >  	last_used = (vq->last_used_idx & (vq->split.vring.num - 1));
> > -	i = virtio32_to_cpu(_vq->vdev,
> > -			vq->split.vring.used->ring[last_used].id);
> > -	*len = virtio32_to_cpu(_vq->vdev,
> > -			vq->split.vring.used->ring[last_used].len);
> > +	i = vring_read_split_used_id(vq, last_used);
> > +	*len = vring_read_split_used_len(vq, last_used);
> >
> >  	if (unlikely(i >= vq->split.vring.num)) {
> >  		BAD_RING(vq, "id %u out of range\n", i);
> > @@ -923,8 +968,7 @@ static bool virtqueue_poll_split(struct virtqueue *_vq, unsigned int last_used_i
> >  {
> >  	struct vring_virtqueue *vq = to_vvq(_vq);
> >
> > -	return (u16)last_used_idx != virtio16_to_cpu(_vq->vdev,
> > -			vq->split.vring.used->idx);
> > +	return (u16)last_used_idx != vring_read_split_used_idx(vq);
> >  }
> >
> >  static bool virtqueue_enable_cb_delayed_split(struct virtqueue *_vq)
> > @@ -1701,10 +1745,10 @@ static void detach_buf_packed(struct vring_virtqueue *vq,
> >  static inline bool is_used_desc_packed(const struct vring_virtqueue *vq,
> >  				       u16 idx, bool used_wrap_counter)
> >  {
> > -	bool avail, used;
> >  	u16 flags;
> > +	bool avail, used;
> >
> > -	flags = le16_to_cpu(vq->packed.vring.desc[idx].flags);
> > +	flags = vring_read_packed_desc_flags(vq, idx);
> >  	avail = !!(flags & (1 << VRING_PACKED_DESC_F_AVAIL));
> >  	used = !!(flags & (1 << VRING_PACKED_DESC_F_USED));
> >
> > @@ -1751,8 +1795,8 @@ static void *virtqueue_get_buf_ctx_packed(struct virtqueue *_vq,
> >  	last_used_idx = READ_ONCE(vq->last_used_idx);
> >  	used_wrap_counter = packed_used_wrap_counter(last_used_idx);
> >  	last_used = packed_last_used(last_used_idx);
> > -	id = le16_to_cpu(vq->packed.vring.desc[last_used].id);
> > -	*len = le32_to_cpu(vq->packed.vring.desc[last_used].len);
> > +	id = vring_read_packed_desc_id(vq, last_used);
> > +	*len = vring_read_packed_desc_len(vq, last_used);
> >
> >  	if (unlikely(id >= vq->packed.vring.num)) {
> >  		BAD_RING(vq, "id %u out of range\n", id);
> > --
> > 2.52.0
> >


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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-31 10:28 [PATCH v3] virtio_ring: Add READ_ONCE annotations for device-writable fields Johannes Thumshirn
2026-02-03  8:27 ` Xuan Zhuo
2026-02-03 11:46   ` Johannes Thumshirn
2026-02-03 12:02   ` Michael S. Tsirkin [this message]
2026-02-03 17:05     ` David Laight

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=20260203065312-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=eperezma@redhat.com \
    --cc=graf@amazon.com \
    --cc=jasowang@redhat.com \
    --cc=johannes.thumshirn@wdc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux.dev \
    --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 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.