Re: [PATCH v2 0/3] Improve lock annotations

2025-02-07 Thread David Marchand
On Thu, Dec 12, 2024 at 5:02 PM David Marchand wrote: > > A recent bug (see 22aa9a9c7099 ("vhost: fix deadlock in Rx async path")) > made more visible a gap in the clang thread safety annotations that > DPDK uses: no distinction is made between releasing a read lock and > releasing a write lock. >

Re: [PATCH v2 0/3] Improve lock annotations

2024-12-13 Thread David Marchand
On Thu, Dec 12, 2024 at 5:02 PM David Marchand wrote: > > A recent bug (see 22aa9a9c7099 ("vhost: fix deadlock in Rx async path")) > made more visible a gap in the clang thread safety annotations that > DPDK uses: no distinction is made between releasing a read lock and > releasing a write lock. >

[PATCH v2 0/3] Improve lock annotations

2024-12-12 Thread David Marchand
A recent bug (see 22aa9a9c7099 ("vhost: fix deadlock in Rx async path")) made more visible a gap in the clang thread safety annotations that DPDK uses: no distinction is made between releasing a read lock and releasing a write lock. Clang 3.6 and later offers improved thread safety checks. Markin