linux-kernel - Re: [PATCH v2 1/1] mm: page_alloc: skip over regions of invalid pfns on UMA

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180123202700.GA5565@bombadil.infradead.org>
Date:   Tue, 23 Jan 2018 12:27:00 -0800
From:   Matthew Wilcox <willy@...radead.org>
To:     Eugeniu Rosca <erosca@...adit-jv.com>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Michal Hocko <mhocko@...e.com>,
        Catalin Marinas <catalin.marinas@....com>,
        Ard Biesheuvel <ard.biesheuvel@...aro.org>,
        Steven Sistare <steven.sistare@...cle.com>,
        AKASHI Takahiro <takahiro.akashi@...aro.org>,
        Pavel Tatashin <pasha.tatashin@...cle.com>,
        Gioh Kim <gi-oh.kim@...fitbricks.com>,
        Heiko Carstens <heiko.carstens@...ibm.com>,
        Wei Yang <richard.weiyang@...il.com>,
        Miles Chen <miles.chen@...iatek.com>,
        Vlastimil Babka <vbabka@...e.cz>, Mel Gorman <mgorman@...e.de>,
        Johannes Weiner <hannes@...xchg.org>,
        Paul Burton <paul.burton@...s.com>,
        James Hartley <james.hartley@...s.com>,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v2 1/1] mm: page_alloc: skip over regions of invalid pfns
 on UMA

On Tue, Jan 23, 2018 at 08:00:36PM +0100, Eugeniu Rosca wrote:
> Hi Matthew,
> 
> On Mon, Jan 22, 2018 at 04:45:51PM -0800, Matthew Wilcox wrote:
> > On Mon, Jan 22, 2018 at 09:25:30PM +0100, Eugeniu Rosca wrote:
> > > Here is what I came up with, based on your proposal:
> > 
> > Reviewed-by: Matthew Wilcox <mawilcox@...rosoft.com>
> 
> Apologies for not knowing the process. Should I include the
> `Reviewed-by` in the description of the next patch or will it be
> done by the maintainer who will hopefully pick up the patch?

It's OK to not know the process ;-)

The next step is for you to integrate the changes you made here into a
fresh patch against mainline, and then add my Reviewed-by: tag underneath
your Signed-off-by: line.