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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9657EC433EF for ; Tue, 10 May 2022 04:26:02 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id CFB816B0072; Tue, 10 May 2022 00:26:01 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id CAA5B6B0073; Tue, 10 May 2022 00:26:01 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id B71476B0074; Tue, 10 May 2022 00:26:01 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id A7FC36B0072 for ; Tue, 10 May 2022 00:26:01 -0400 (EDT) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id 7A9A7FFB for ; Tue, 10 May 2022 04:26:01 +0000 (UTC) X-FDA: 79448545722.11.8B3C87E Received: from out30-57.freemail.mail.aliyun.com (out30-57.freemail.mail.aliyun.com [115.124.30.57]) by imf20.hostedemail.com (Postfix) with ESMTP id 306B91C00A2 for ; Tue, 10 May 2022 04:25:50 +0000 (UTC) X-Alimail-AntiSpam:AC=PASS;BC=-1|-1;BR=01201311R271e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01e04357;MF=baolin.wang@linux.alibaba.com;NM=1;PH=DS;RN=31;SR=0;TI=SMTPD_---0VCp29EM_1652156751; Received: from 30.15.214.13(mailfrom:baolin.wang@linux.alibaba.com fp:SMTPD_---0VCp29EM_1652156751) by smtp.aliyun-inc.com(127.0.0.1); Tue, 10 May 2022 12:25:53 +0800 Message-ID: <0db300f4-8a91-b330-5c6f-bbc63cf2f151@linux.alibaba.com> Date: Tue, 10 May 2022 12:26:32 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Subject: Re: [PATCH v3 0/3] Fix CONT-PTE/PMD size hugetlb issue when unmapping or migrating To: Andrew Morton Cc: mike.kravetz@oracle.com, catalin.marinas@arm.com, will@kernel.org, songmuchun@bytedance.com, tsbogend@alpha.franken.de, James.Bottomley@HansenPartnership.com, deller@gmx.de, mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org, hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com, borntraeger@linux.ibm.com, svens@linux.ibm.com, ysato@users.osdn.me, dalias@libc.org, davem@davemloft.net, arnd@arndb.de, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org, linux-mips@vger.kernel.org, linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-arch@vger.kernel.org, linux-mm@kvack.org References: <20220509210404.6a43aff15d0d6b3af0741001@linux-foundation.org> From: Baolin Wang In-Reply-To: <20220509210404.6a43aff15d0d6b3af0741001@linux-foundation.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: 306B91C00A2 X-Stat-Signature: 4kwcsj43nbfp5fwubj55h9yg9o895jdh X-Rspam-User: Authentication-Results: imf20.hostedemail.com; dkim=none; dmarc=pass (policy=none) header.from=alibaba.com; spf=pass (imf20.hostedemail.com: domain of baolin.wang@linux.alibaba.com designates 115.124.30.57 as permitted sender) smtp.mailfrom=baolin.wang@linux.alibaba.com X-HE-Tag: 1652156750-196501 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000216, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 5/10/2022 12:04 PM, Andrew Morton wrote: > On Tue, 10 May 2022 11:45:57 +0800 Baolin Wang wrote: > >> Hi, >> >> Now migrating a hugetlb page or unmapping a poisoned hugetlb page, we'll >> use ptep_clear_flush() and set_pte_at() to nuke the page table entry >> and remap it, and this is incorrect for CONT-PTE or CONT-PMD size hugetlb >> page, > > It would be helpful to describe why it's wrong. Something like "should > use huge_ptep_clear_flush() and huge_ptep_clear_flush() for this > purpose"? Sorry for the confusing description. I described the problem explicitly in each patch's commit message. https://lore.kernel.org/all/ea5abf529f0997b5430961012bfda6166c1efc8c.1652147571.git.baolin.wang@linux.alibaba.com/ https://lore.kernel.org/all/730ea4b6d292f32fb10b7a4e87dad49b0eb30474.1652147571.git.baolin.wang@linux.alibaba.com/ > >> which will cause potential data consistent issue. This patch set >> will change to use hugetlb related APIs to fix this issue, please find >> details in each patch. Thanks. > > Is a cc:stable needed here? And are we able to identify a target for a > Fixes: tag? I think need a cc:stable tag, however I am not sure the target fixes tag, since we should trace back to the introduction of CONT-PTE/PMD hugetlb? 66b3923a1a0f ("arm64: hugetlb: add support for PTE contiguous bit")