linux-kernel - Re: [PATCH] mm/arch: Provide pud

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: <20240326132726.67e82559a928ac1636c8050c@linux-foundation.org>
Date: Tue, 26 Mar 2024 13:27:26 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: peterx@...hat.com
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org, SeongJae Park
 <sj@...nel.org>, Jason Gunthorpe <jgg@...dia.com>, Mike Rapoport
 <rppt@...nel.org>, Matthew Wilcox <willy@...radead.org>, kernel test robot
 <lkp@...el.com>
Subject: Re: [PATCH] mm/arch: Provide pud_pfn() fallback

On Sat, 23 Mar 2024 11:16:43 -0400 peterx@...hat.com wrote:

> From: Peter Xu <peterx@...hat.com>
> 
> The comment in the code explains the reasons.  We took a different approach
> comparing to pmd_pfn() by providing a fallback function.
> 
> Another option is to provide some lower level config options (compare to
> HUGETLB_PAGE or THP) to identify which layer an arch can support for such
> huge mappings.  However that can be an overkill.
> 
> ...
>
> If we care about per-commit build errors (and if it is ever feasible to
> reorder), we can move this patch to be before the patch "mm/gup: handle
> huge pud for follow_pud_mask()" in mm-unstable to unbreak build on that
> commit.

I temporarily disabled that whole series a few days ago.  Because of
multiple build issues, iirc.

Let's make that permanent.  Please redo the whole series against
mm-unstable and resend?