Received-SPF: pass (google.com: domain of linux-kernel+bounces-188118-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Precedence: bulk
MIME-Version: 1.0
References: <20240523132139.289719-1-peterx@redhat.com>
In-Reply-To: <20240523132139.289719-1-peterx@redhat.com>
From: Pasha Tatashin <pasha.tatashin@soleen.com>
Date: Thu, 23 May 2024 19:23:19 -0400
Message-ID: <CA+CK2bDhAOto1A+TAvGSuNzNTTUd9FZ4m3wV_3rou6AfXJzXzA@mail.gmail.com>
Subject: Re: [PATCH] mm/debug_vm_pgtable: Drop RANDOM_ORVALUE trick
To: Peter Xu <peterx@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, 
	Andrew Morton <akpm@linux-foundation.org>, David Hildenbrand <david@redhat.com>, 
	"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>, Gavin Shan <gshan@redhat.com>, 
	Anshuman Khandual <anshuman.khandual@arm.com>, Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, May 23, 2024 at 9:21=E2=80=AFAM Peter Xu <peterx@redhat.com> wrote:
>
> Macro RANDOM_ORVALUE was used to make sure the pgtable entry will be
> populated with !none data in clear tests.
>
> The RANDOM_ORVALUE tried to cover mostly all the bits in a pgtable entry,
> even if there's no discussion on whether all the bits will be vaild.  Bot=
h
> S390 and PPC64 have their own masks to avoid touching some bits.  Now it'=
s
> the turn for x86_64.
>
> The issue is there's a recent report from Mikhail Gavrilov showing that
> this can cause a warning with the newly added pte set check in commit
> 8430557fc5 on writable v.s. userfaultfd-wp bit, even though the check
> itself was valid, the random pte is not.  We can choose to mask more bits
> out.
>
> However the need to have such random bits setup is questionable, as now
> it's already guaranteed to be true on below:
>
>   - For pte level, the pgtable entry will be installed with value from
>     pfn_pte(), where pfn points to a valid page.  Hence the pte will be
>     !none already if populated with pfn_pte().
>
>   - For upper-than-pte level, the pgtable entry should contain a director=
y
>     entry always, which is also !none.
>
> All the cases look like good enough to test a pxx_clear() helper.  Instea=
d
> of extending the bitmask, drop the "set random bits" trick completely.  A=
dd
> some warning guards to make sure the entries will be !none before clear()=
.
>
> Cc: David Hildenbrand <david@redhat.com>
> Cc: Pavel Tatashin <pasha.tatashin@soleen.com>
> Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
> Cc: Gavin Shan <gshan@redhat.com>
> Cc: Anshuman Khandual <anshuman.khandual@arm.com>
> Reported-by: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
> Tested-by: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
> Link: https://lore.kernel.org/r/CABXGCsMB9A8-X+Np_Q+fWLURYL_0t3Y-MdoNabDM=
-Lzk58-DGA@mail.gmail.com
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
>  mm/debug_vm_pgtable.c | 31 +++++--------------------------
>  1 file changed, 5 insertions(+), 26 deletions(-)

Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>