linux-kernel - Re: linux-next: Tree for May 3

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]

Date:   Wed, 11 May 2022 16:40:33 +0200
From:   Christoph Hellwig <hch@....de>
To:     Mike Rapoport <rppt@...nel.org>
Cc:     Christoph Hellwig <hch@....de>, Conor.Dooley@...rochip.com,
        sfr@...b.auug.org.au, linux-next@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org
Subject: Re: linux-next: Tree for May 3

On Wed, May 11, 2022 at 05:37:50PM +0300, Mike Rapoport wrote:
> Presuming that devices see [0x1000200000-0x103fffffff] as
> [0x200000-0x3fffffff] we may try something like
> 
> 	min = memblock_start_of_DRAM();
> 	max = min + 0xffffffff;
> 
> 	if (flags & SWIOTLB_ANY)
> 		max = MEMBLOCK_ALLOC_ACCESSIBLE;
> 
> 	tlb = memblock_alloc_try_nid(bytes, PAGE_SIZE, min, max, NUMA_NO_NODE);

While there is still no guarantee the first 32-bits worth of DRAM
are actually mapped to a usable address, this looks like a much better
default than what we have right now.