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 DF557C433F5 for ; Wed, 11 May 2022 17:28:03 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 5EECF6B0073; Wed, 11 May 2022 13:28:03 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 5995A6B0074; Wed, 11 May 2022 13:28:03 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 43A506B0075; Wed, 11 May 2022 13:28:03 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0012.hostedemail.com [216.40.44.12]) by kanga.kvack.org (Postfix) with ESMTP id 35E5A6B0073 for ; Wed, 11 May 2022 13:28:03 -0400 (EDT) Received: from smtpin23.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 065B83030C for ; Wed, 11 May 2022 17:28:02 +0000 (UTC) X-FDA: 79454145246.23.0C00F47 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by imf27.hostedemail.com (Postfix) with ESMTP id 0B408400A8 for ; Wed, 11 May 2022 17:27:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1652290081; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=cS5E6UtIkG/hFuUJaz85MfZ3xWqLO1I63lqGQCOfSNw=; b=h9Kkg6bxy6vsZ5MkHmLGhdoNjLqMKp0k5xsGMQWAyZL8wEgrXXK9eX34YqTfjfFletoHAx 10tf88VX+oMKhtdyw/C2fyk0EPTowCJAglo2aNb8kqUvrKRwrw34IcFuQEXoDSSrVZTWAq H+BkTL9nsIB0CRdf8ZnFAjvtJzCDVHs= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-608-9nUz0nhVNtaOEPv92gF_rQ-1; Wed, 11 May 2022 13:27:58 -0400 X-MC-Unique: 9nUz0nhVNtaOEPv92gF_rQ-1 Received: by mail-wm1-f70.google.com with SMTP id c62-20020a1c3541000000b0038ec265155fso3120176wma.6 for ; Wed, 11 May 2022 10:27:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:organization:in-reply-to :content-transfer-encoding; bh=cS5E6UtIkG/hFuUJaz85MfZ3xWqLO1I63lqGQCOfSNw=; b=m+0cT8k1zT9Hb5JvwE3XVQJFBcqo1jr8YCtcdD97g7BnQtht/k9hWZA69c+S9qzYdU 15Z9hzc/njUFSmNtxdAq8eCi9arInSeWW5bIlQHLGp2zgq1kTKQyE8OnJYrw/5wIr503 TIqsQ5uqLPEoqgryaDuYMlgrUKnFd+15F1GuIY6Mmbr+RNslsSzF7+nigf/7uxTuTo2m DKqrq7Ds3UAqQFHrjivzQqO+jd8XRIX5TFVhrPIWmAZjWWPINaqP8LZBfnjwK/x8wgxa Rhbzu+y+kOe35Y5W8KFbNMYMiSFzVTNh32IcbCV8cJnnwBYfgyMNfyD5Ihj9FaGO6qjj EcMw== X-Gm-Message-State: AOAM530U+rTWBARBy9ZyLMW8l7j8J0WIGPquwgR/Cqzy0KT6U+BmVBXo riWG+/+0hjqgd3O01VLTDdg+Q2SJyhftX6jA60DEUHhU87zJqYha9BAzISPKKhemjAkxAGlvonm ED642n4fwBVg= X-Received: by 2002:a7b:c4d8:0:b0:393:fecd:2718 with SMTP id g24-20020a7bc4d8000000b00393fecd2718mr6012813wmk.23.1652290077483; Wed, 11 May 2022 10:27:57 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzBTzXKBES23B3psLkzxI9cGRRJgtAEIRhBp8LvQHOEvCQMFPcLMWgEwEKr1C169Li1EVKAzw== X-Received: by 2002:a7b:c4d8:0:b0:393:fecd:2718 with SMTP id g24-20020a7bc4d8000000b00393fecd2718mr6012790wmk.23.1652290077160; Wed, 11 May 2022 10:27:57 -0700 (PDT) Received: from ?IPV6:2003:cb:c701:700:2393:b0f4:ef08:bd51? (p200300cbc70107002393b0f4ef08bd51.dip0.t-ipconnect.de. [2003:cb:c701:700:2393:b0f4:ef08:bd51]) by smtp.gmail.com with ESMTPSA id r12-20020a5d694c000000b0020c5253d8c3sm2174483wrw.15.2022.05.11.10.27.54 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 11 May 2022 10:27:55 -0700 (PDT) Message-ID: <55e85b3e-dd6a-1dc2-719d-c6be9d5124c0@redhat.com> Date: Wed, 11 May 2022 19:27:53 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: [PATCH v4 2/3] mm: rmap: Fix CONT-PTE/PMD size hugetlb issue when migration To: Baolin Wang , akpm@linux-foundation.org, mike.kravetz@oracle.com Cc: 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.sourceforge.jp, 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: From: David Hildenbrand Organization: Red Hat In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Authentication-Results: imf27.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b=h9Kkg6bx; dmarc=pass (policy=none) header.from=redhat.com; spf=none (imf27.hostedemail.com: domain of david@redhat.com has no SPF policy when checking 170.10.133.124) smtp.mailfrom=david@redhat.com X-Rspamd-Server: rspam06 X-Rspamd-Queue-Id: 0B408400A8 X-Rspam-User: X-Stat-Signature: crxynjrw4wfmeqdnsms4nxr116doscqt X-HE-Tag: 1652290079-844314 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 11.05.22 14:04, Baolin Wang wrote: > On some architectures (like ARM64), it can support CONT-PTE/PMD size > hugetlb, which means it can support not only PMD/PUD size hugetlb: > 2M and 1G, but also CONT-PTE/PMD size: 64K and 32M if a 4K page > size specified. > > When migrating a hugetlb page, we will get the relevant page table > entry by huge_pte_offset() only once to nuke it and remap it with > a migration pte entry. This is correct for PMD or PUD size hugetlb, > since they always contain only one pmd entry or pud entry in the > page table. > > However this is incorrect for CONT-PTE and CONT-PMD size hugetlb, > since they can contain several continuous pte or pmd entry with > same page table attributes. So we will nuke or remap only one pte > or pmd entry for this CONT-PTE/PMD size hugetlb page, which is > not expected for hugetlb migration. The problem is we can still > continue to modify the subpages' data of a hugetlb page during > migrating a hugetlb page, which can cause a serious data consistent > issue, since we did not nuke the page table entry and set a > migration pte for the subpages of a hugetlb page. > > To fix this issue, we should change to use huge_ptep_clear_flush() > to nuke a hugetlb page table, and remap it with set_huge_pte_at() > and set_huge_swap_pte_at() when migrating a hugetlb page, which > already considered the CONT-PTE or CONT-PMD size hugetlb. > > Signed-off-by: Baolin Wang > Reviewed-by: Muchun Song > Reviewed-by: Mike Kravetz Makes sense to me. Acked-by: David Hildenbrand -- Thanks, David / dhildenb