[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <99e36842-f267-4881-8c5f-45b41df76490@wdc.com>
Date: Tue, 27 Jan 2026 08:54:49 +0000
From: Johannes Thumshirn <Johannes.Thumshirn@....com>
To: Alexander Graf <graf@...zon.com>, "virtualization@...ts.linux.dev"
<virtualization@...ts.linux.dev>
CC: "mst@...hat.com" <mst@...hat.com>, "jasowang@...hat.com"
<jasowang@...hat.com>, "xuanzhuo@...ux.alibaba.com"
<xuanzhuo@...ux.alibaba.com>, "eperezma@...hat.com" <eperezma@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC 0/3] virtio: silence KCSAN warnings
On 1/27/26 9:48 AM, Alexander Graf wrote:
> 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"?
>
Oh indeed, there is a __data_racy annotation. Let me try it!
Powered by blists - more mailing lists