linux-kernel - Re: [PATCH v1] vdpa/mlx5: Restore the hardware used index after change map

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <c3760a4c-5047-8a03-2935-0b9b5a682dbb@oracle.com>
Date:   Fri, 19 Feb 2021 19:00:00 -0800
From:   Si-Wei Liu <si-wei.liu@...cle.com>
To:     Jason Wang <jasowang@...hat.com>, Eli Cohen <elic@...dia.com>
Cc:     mst@...hat.com, virtualization@...ts.linux-foundation.org,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        lulu@...hat.com
Subject: Re: [PATCH v1] vdpa/mlx5: Restore the hardware used index after
 change map



On 2/19/2021 6:38 PM, Jason Wang wrote:
>>>
>>>
>>> Right now the value is exposed to userspace via GET_VRING_BASE, so 
>>> only last_avail_idx is synced. If we need sync last_used_idx, we 
>>> should also sync pending indices which requires more thoughts.
>> Technically it doesn't sound right - crossing the boundary a bit even 
>> with simplified form of assumption. But depending on how userspace 
>> could make use of this API, it doesn't seem it breaks existing 
>> functionality for the moment.
>
>
> I don't get here, maybe you can explain a little bit more? 
Please refer to the email I just sent.

https://lore.kernel.org/lkml/033b0806-4037-5755-a1fa-91dbb58bab2e@oracle.com/

-Siwei