[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210713191244.553680171f9fab3bf6e0889b@linux-foundation.org>
Date: Tue, 13 Jul 2021 19:12:44 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Matthew Wilcox (Oracle)" <willy@...radead.org>
Cc: Mina Almasry <almasrymina@...gle.com>,
YueHaibing <yuehaibing@...wei.com>,
Axel Rasmussen <axelrasmussen@...gle.com>,
Peter Xu <peterx@...hat.com>,
Mike Kravetz <mike.kravetz@...cle.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: Make copy_huge_page() always available
On Mon, 12 Jul 2021 16:32:07 +0100 "Matthew Wilcox (Oracle)" <willy@...radead.org> wrote:
> Rewrite copy_huge_page() and move it into mm/util.c so it's always
> available. Fixes an exposure of uninitialised memory on configurations
> with HUGETLB and UFFD enabled and MIGRATION disabled.
Wait. Exposing uninitialized memory is serious. Can we please include
full info on this flaw and decide whether a -stable backport is justified?
If not, why not, etc?
Powered by blists - more mailing lists