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
| ||
|
Date: Wed, 27 Jan 2021 13:09:25 -0600 From: Rob Herring <robh+dt@...nel.org> To: Robin Murphy <robin.murphy@....com> Cc: Frank Rowand <frowand.list@...il.com>, Christoph Hellwig <hch@....de>, Marek Szyprowski <m.szyprowski@...sung.com>, Joerg Roedel <joro@...tes.org>, Matthias Brugger <matthias.bgg@...il.com>, Will Deacon <will@...nel.org>, Krzysztof Kozlowski <krzk@...nel.org>, Tomasz Figa <tfiga@...gle.com>, "moderated list:ARM/Mediatek SoC support" <linux-mediatek@...ts.infradead.org>, srv_heupstream <srv_heupstream@...iatek.com>, devicetree@...r.kernel.org, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>, Linux IOMMU <iommu@...ts.linux-foundation.org>, Nicolas Boichat <drinkcat@...omium.org>, Yong Wu <yong.wu@...iatek.com>, Paul Kocialkowski <paul.kocialkowski@...tlin.com> Subject: Re: [PATCH v2] of/device: Update dma_range_map only when dev has valid dma-ranges On Wed, Jan 27, 2021 at 7:13 AM Robin Murphy <robin.murphy@....com> wrote: > > [ + Christoph, Marek ] > > On 2021-01-27 13:00, Paul Kocialkowski wrote: > > Hi, > > > > On Tue 19 Jan 21, 18:52, Yong Wu wrote: > >> The commit e0d072782c73 ("dma-mapping: introduce DMA range map, > >> supplanting dma_pfn_offset") always update dma_range_map even though it was > >> already set, like in the sunxi_mbus driver. the issue is reported at [1]. > >> This patch avoid this(Updating it only when dev has valid dma-ranges). > >> > >> Meanwhile, dma_range_map contains the devices' dma_ranges information, > >> This patch moves dma_range_map before of_iommu_configure. The iommu > >> driver may need to know the dma_address requirements of its iommu > >> consumer devices. > > > > Just a gentle ping on this issue, it would be nice to have this fix merged > > ASAP, in the next RC :) > > Ack to that - Rob, Frank, do you want to take this through the OF tree, > or shall we take it through the DMA-mapping tree like the original culprit? I've already got some fixes queued up and can take it. Suggested-by doesn't mean you are happy with the implementation. So Acked-by or Reviewed-by? Rob
Powered by blists - more mailing lists