linux-kernel - Re: remoteproc DMA API abuse status

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: <011dac94-cfe0-d276-980a-b8ffe1447521@foss.st.com>
Date:   Fri, 25 Jun 2021 09:27:09 +0200
From:   Arnaud POULIQUEN <arnaud.pouliquen@...s.st.com>
To:     Mathieu Poirier <mathieu.poirier@...aro.org>,
        Christoph Hellwig <hch@....de>
CC:     Ohad Ben-Cohen <ohad@...ery.com>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        <linux-remoteproc@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: remoteproc DMA API abuse status

Hello Mathieu,

On 6/24/21 9:35 PM, Mathieu Poirier wrote:
> Good day Christoph,
> 
> On Wed, Jun 23, 2021 at 03:43:07PM +0200, Christoph Hellwig wrote:
>> Hi remoteproc maintainers,
>>
>> did you make any progress to get remoteproc out of creating fake
>> devices that fake their dma ops status and the abuse of
>> dma_declare_coherent_memory in removeproc_virtio?  I remember we had
>> a discussion on this a long time ago, and there was an unfinished
>> patchset to change the memory pool handling.  What happened to all that?
> 
> I believe the conversation and patchset you are referring to are pre-dating my
> time in this subsystem.  To make sure I am looking at the right thing, can you
> (or anyone else) point me to that discussion and related patches?

2 references:

1)Previous discussion thread on the topic:

https://patchwork.kernel.org/project/linux-remoteproc/patch/AOKowLclCbOCKxyiJ71WeNyuAAj2q8EUtxrXbyky5E@cp7-web-042.plabs.ch/

2) My patchset related to the refactoring of remoteproc virtio which tries to
address the point by creating a remoteproc platform driver and declaring a
virtio subnode in the device tree remoteproc node.

https://lkml.org/lkml/2020/4/16/1817

No time yet on my side to come back on the patchset :(

Regards,
Arnaud

> 
> Thanks,
> Mathieu
>