linux-kernel - Re: [PATCH stable v5.10 0/7] arm64: Default to 32-bit wide ZONE

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: <YNWtyJaDY17829g9@kroah.com>
Date:   Fri, 25 Jun 2021 12:19:52 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Kefeng Wang <wangkefeng.wang@...wei.com>
Cc:     Jing Xiangfeng <jingxiangfeng@...wei.com>,
        Nicolas Saenz Julienne <nsaenzjulienne@...e.de>,
        catalin.marinas@....com, will@...nel.org,
        akpm@...ux-foundation.org, guohanjun@...wei.com,
        sudeep.holla@....com, song.bao.hua@...ilicon.com, ardb@...nel.org,
        anshuman.khandual@....com, stable@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, Li Huafei <lihuafei1@...wei.com>
Subject: Re: [PATCH stable v5.10 0/7] arm64: Default to 32-bit wide ZONE_DMA

On Wed, Jun 23, 2021 at 04:01:10PM +0800, Kefeng Wang wrote:
> 
> 
> On 2021/6/23 15:34, Greg KH wrote:
> > On Wed, Jun 23, 2021 at 03:25:10PM +0800, Kefeng Wang wrote:
> > > 
> > > 
> > > On 2021/6/23 15:12, Greg KH wrote:
> > > > On Wed, Jun 23, 2021 at 02:59:59PM +0800, Kefeng Wang wrote:
> > > > > Hi Greg,
> > > > > 
> > > > > There are two more patches about the ZONE_DMA[32] changes,
> > > > 
> > > > What ZONE_DMA changes?
> > > 
> > > See the subject, [PATCH stable v5.10 0/7] arm64: Default to 32-bit wide
> > > ZONE_DMA, We asked the ARM64 ZONE_DMA change backport before, link[1]
> 
> Let's inline the link:
> https://lore.kernel.org/lkml/20210303073319.2215839-1-jingxiangfeng@huawei.com/
> 
> The following 7 patches(we asked from link) has merged into lts5.10(tag:
> v5.10.22)
> 
>   4d7ed9a49b0c mm: Remove examples from enum zone_type comment
>   8eaef922e938 arm64: mm: Set ZONE_DMA size based on early IORT scan
>   35ec3d09ff6a arm64: mm: Set ZONE_DMA size based on devicetree's dma-ranges
>   a9861e7fa4f8 of: unittest: Add test for of_dma_get_max_cpu_address()
>   18bf6e998d08 of/address: Introduce of_dma_get_max_cpu_address()
>   3fbe62ffbb54 arm64: mm: Move zone_dma_bits initialization into
> zone_sizes_init()
>   407b173adfac arm64: mm: Move reserve_crashkernel() into mem_init()
> 
> but the patch "arm64: mm: Move reserve_crashkernel() into mem_init()"
> has some issue, see the following discussion from Catalin,
> 
> https://lore.kernel.org/linux-devicetree/e60d643e-4879-3fc3-737d-2c145332a6d7@arm.com/
> https://lore.kernel.org/linux-arm-kernel/20201119175556.18681-1-catalin.marinas@arm.com/
> 
> and yes, we met crash in lts5.10 when kexec boot due to "arm64: mm: Move
> reserve_crashkernel() into mem_init()" too, which could be fixed by
> commit 2687275a5843 "arm64: Force NO_BLOCK_MAPPINGS if crashkernel
> reservation is required", and the commit 791ab8b2e3db "arm64: Ignore any DMA
> offsets in the max_zone_phys() calculation" also about DMA set,
> So I only asked the two patches(both in v5.11) related ARM64 ZONE_DMA
> changes backported into lts5.10.

Thanks, all now queued up.

greg k-h