From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 049D9C07E95 for ; Wed, 14 Jul 2021 02:22:27 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 93CA76128E for ; Wed, 14 Jul 2021 02:22:26 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 93CA76128E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id D01AD6B008C; Tue, 13 Jul 2021 22:22:26 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id CD8686B0092; Tue, 13 Jul 2021 22:22:26 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id BA0376B0095; Tue, 13 Jul 2021 22:22:26 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0046.hostedemail.com [216.40.44.46]) by kanga.kvack.org (Postfix) with ESMTP id 94DCA6B008C for ; Tue, 13 Jul 2021 22:22:26 -0400 (EDT) Received: from smtpin13.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id 96D572BA67 for ; Wed, 14 Jul 2021 02:22:25 +0000 (UTC) X-FDA: 78359594250.13.D5038D0 Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) by imf06.hostedemail.com (Postfix) with ESMTP id 2ED65801E4F3 for ; Wed, 14 Jul 2021 02:22:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=B3fKLu6x90gYniUL5gogEh9zBG7fF7DVZEYNuV5m4q0=; b=NtmylrsCgZ2SnKyzsjA02m/cpv Lojz2OtZCoq0uRMf8PJ1ERJm7b4U6OFL3HBn4sYNo0F8qsLxnkDI1Xu9uJde8fY7DlXIGEZHqERMM LQEeUpvKEDDAq9sqPEZp+TaLJPVza+4VOfoF5nBJ4JYSb2FiDCiZkYfCWBhwxTlKEKsX0URFO5RZn cUWANCeH+X8PJT6JLwEddaQSaw/cFaU55CRCo2PvgfaEqEsNyvsOs+gukMhIDmETdWzjM0ttjqt4W JdNk2UNAnqVFCL8qzUMuZLFhv/OrWv8r5gTOvCKrDoXT90VBbahCDaMGw7m4vQbaUKA877XeYFGDF 1377F20w==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1m3UVw-001kkZ-4U; Wed, 14 Jul 2021 02:20:51 +0000 Date: Wed, 14 Jul 2021 03:20:44 +0100 From: Matthew Wilcox To: Andrew Morton Cc: Mina Almasry , YueHaibing , Axel Rasmussen , Peter Xu , Mike Kravetz , Linus Torvalds , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm: Make copy_huge_page() always available Message-ID: References: <20210712153207.39302-1-willy@infradead.org> <20210713191244.553680171f9fab3bf6e0889b@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210713191244.553680171f9fab3bf6e0889b@linux-foundation.org> Authentication-Results: imf06.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=NtmylrsC; spf=none (imf06.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org; dmarc=none X-Stat-Signature: toxquwst37af4oybwobhsa4bai76e55j X-Rspamd-Queue-Id: 2ED65801E4F3 X-Rspamd-Server: rspam01 X-HE-Tag: 1626229345-486670 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Tue, Jul 13, 2021 at 07:12:44PM -0700, Andrew Morton wrote: > On Mon, 12 Jul 2021 16:32:07 +0100 "Matthew Wilcox (Oracle)" 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? Well, the code was only merged this merge window, so as long as it goes in in the next few weeks, there's no need to trouble -stable with it.