linux-kernel - Re: [RFC PATCH 0/7] Untrusted device support for virtio

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <0c61dcbb-ac5b-9815-a4a1-5f93ae640011@redhat.com>
Date:   Thu, 22 Apr 2021 16:19:16 +0800
From:   Jason Wang <jasowang@...hat.com>
To:     Christoph Hellwig <hch@...radead.org>
Cc:     mst@...hat.com, virtualization@...ts.linux-foundation.org,
        linux-kernel@...r.kernel.org, xieyongji@...edance.com,
        stefanha@...hat.com, file@...t.tu-berlin.de, ashish.kalra@....com,
        martin.radev@...ec.fraunhofer.de, konrad.wilk@...cle.com,
        kvm@...r.kernel.org
Subject: Re: [RFC PATCH 0/7] Untrusted device support for virtio


在 2021/4/22 下午2:31, Christoph Hellwig 写道:
> On Wed, Apr 21, 2021 at 11:21:10AM +0800, Jason Wang wrote:
>> The behaivor for non DMA API is kept for minimizing the performance
>> impact.
> NAK.  Everyone should be using the DMA API in a modern world.  So
> treating the DMA API path worse than the broken legacy path does not
> make any sense whatsoever.


I think the goal is not treat DMA API path worse than legacy. The issue 
is that the management layer should guarantee that ACCESS_PLATFORM is 
set so DMA API is guaranteed to be used by the driver. So I'm not sure 
how much value we can gain from trying to 'fix' the legacy path. But I 
can change the behavior of legacy path to match DMA API path.

Thanks