All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: Mina Almasry <almasrymina@google.com>,
	YueHaibing <yuehaibing@huawei.com>,
	Axel Rasmussen <axelrasmussen@google.com>,
	Peter Xu <peterx@redhat.com>,
	Mike Kravetz <mike.kravetz@oracle.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Make copy_huge_page() always available
Date: Tue, 13 Jul 2021 19:12:44 -0700	[thread overview]
Message-ID: <20210713191244.553680171f9fab3bf6e0889b@linux-foundation.org> (raw)
In-Reply-To: <20210712153207.39302-1-willy@infradead.org>

On Mon, 12 Jul 2021 16:32:07 +0100 "Matthew Wilcox (Oracle)" <willy@infradead.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?


  parent reply	other threads:[~2021-07-14  2:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-12 15:32 [PATCH] mm: Make copy_huge_page() always available Matthew Wilcox (Oracle)
2021-07-12 17:52 ` Mike Kravetz
2021-07-12 19:32   ` Mina Almasry
2021-07-12 19:32     ` Mina Almasry
2021-07-14  2:12 ` Andrew Morton [this message]
2021-07-14  2:20   ` Matthew Wilcox
2021-07-14 16:09     ` Linus Torvalds
2021-07-14 16:09       ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210713191244.553680171f9fab3bf6e0889b@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=almasrymina@google.com \
    --cc=axelrasmussen@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=peterx@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@infradead.org \
    --cc=yuehaibing@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.