From: Alexander Graf <graf@amazon.com>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>,
<virtualization@lists.linux.dev>
Cc: <mst@redhat.com>, <jasowang@redhat.com>,
<xuanzhuo@linux.alibaba.com>, <eperezma@redhat.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC 0/3] virtio: silence KCSAN warnings
Date: Tue, 27 Jan 2026 09:47:43 +0100 [thread overview]
Message-ID: <fed4ce78-37c5-4bb5-86de-6d60f053dbf3@amazon.com> (raw)
In-Reply-To: <20260127083926.865555-1-johannes.thumshirn@wdc.com>
On 27.01.26 09:39, Johannes Thumshirn wrote:
> When booting a Qemu VM whith KCSAN to debug filesystem races I
> encountered a bunch of KCSAN splats in virtio.
>
> I suspect them to be false positives.
>
> I decided to send this as an RFC patchset, as I have no prior knowledge
> of virtio.
All of these looks like KCSAN was just detecting the hypervisor writing
data. Is there a more generic way we can capture that in the virtio
helpers? So instead of patching the consumers of functions such as
vring_interrupt(), can we annotate the whole vring struct as "ignore for
KCSAN"?
Alex
Amazon Web Services Development Center Germany GmbH
Tamara-Danz-Str. 13
10243 Berlin
Geschaeftsfuehrung: Christof Hellmis, Andreas Stieger
Eingetragen am Amtsgericht Charlottenburg unter HRB 257764 B
Sitz: Berlin
Ust-ID: DE 365 538 597
next prev parent reply other threads:[~2026-01-27 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 8:39 [PATCH RFC 0/3] virtio: silence KCSAN warnings Johannes Thumshirn
2026-01-27 8:39 ` [PATCH RFC 1/3] virtio: silence KCSAN warning in virtqueue_kick_prepare Johannes Thumshirn
2026-01-27 8:39 ` [PATCH RFC 2/3] virtio: silence KCSAN warning in virtqueue_get_buf_ctx_split Johannes Thumshirn
2026-01-27 8:39 ` [PATCH RFC 3/3] virtio: silence KCSAN warning in vring_interrupt Johannes Thumshirn
2026-01-27 8:47 ` Alexander Graf [this message]
2026-01-27 8:54 ` [PATCH RFC 0/3] virtio: silence KCSAN warnings Johannes Thumshirn
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=fed4ce78-37c5-4bb5-86de-6d60f053dbf3@amazon.com \
--to=graf@amazon.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox