05/03/2025 10:52, Maxime Coquelin:
>
> On 3/5/25 10:12 AM, David Marchand wrote:
> > vc_req_out->vq->iotlb_lock is taken twice on the same thread:
> > vc_req_out->vq refers to vc_req->vq (after a memcpy), which itself
> > is a reference to the vq.
> >
> > clang probably does not detect that the s
vc_req_out->vq->iotlb_lock is taken twice on the same thread:
vc_req_out->vq refers to vc_req->vq (after a memcpy), which itself
is a reference to the vq.
clang probably does not detect that the same object is already locked as
it does not track object referencies.
Finish the incomplete and incor
On 3/5/25 10:12 AM, David Marchand wrote:
vc_req_out->vq->iotlb_lock is taken twice on the same thread:
vc_req_out->vq refers to vc_req->vq (after a memcpy), which itself
is a reference to the vq.
clang probably does not detect that the same object is already locked as
it does not track objec
>
> clang probably does not detect that the same object is already locked as it
> does
> not track object referencies.
>
> Finish the incomplete and incorrect cleanup and only refer to the
> &vq->iotlb_lock
> capability (required by vhost_iova_to_vva).
>
> Fixes: 88c73b5434e6 ("vhost/crypto: f
4 matches
Mail list logo