linux-kernel - Re: [PATCH 0/2] dma-mapping, remoteproc: Fix dma_mem leak after rproc

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: <20220622162540.GA1606016@p14s>
Date:   Wed, 22 Jun 2022 10:25:40 -0600
From:   Mathieu Poirier <mathieu.poirier@...aro.org>
To:     Christoph Hellwig <hch@....de>
Cc:     Mark-PK Tsai <mark-pk.tsai@...iatek.com>,
        bjorn.andersson@...aro.org, robin.murphy@....com,
        m.szyprowski@...sung.com, matthias.bgg@...il.com,
        linux-remoteproc@...r.kernel.org, linux-kernel@...r.kernel.org,
        iommu@...ts.linux-foundation.org,
        linux-arm-kernel@...ts.infradead.org,
        linux-mediatek@...ts.infradead.org, yj.chiang@...iatek.com
Subject: Re: [PATCH 0/2] dma-mapping, remoteproc: Fix dma_mem leak after
 rproc_shutdown

On Sat, Apr 23, 2022 at 07:46:50PM +0200, Christoph Hellwig wrote:
> Sigh.  In theory drivers should never declare coherent memory like
> this, and there has been some work to fix remoteproc in that regard.
> 
> But I guess until that is merged we'll need somthing like this fix.

Should I take this in the remoteproc tree?  If so, can I get an RB?

Thanks,
Mathieu