From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, rientjes@google.com, pjt@google.com,
weixugc@google.com, gthelen@google.com, mingo@redhat.com,
will@kernel.org, rppt@kernel.org, dave.hansen@linux.intel.com,
hpa@zytor.com, aneesh.kumar@linux.ibm.com, jirislaby@kernel.org,
songmuchun@bytedance.com, qydwhotmail@gmail.com,
hughd@google.com, ziy@nvidia.com
Subject: Re: [PATCH v2 1/3] mm/debug_vm_pgtable: remove pte entry from the page table
Date: Fri, 21 Jan 2022 09:07:25 +0530 [thread overview]
Message-ID: <406f41ab-5ed9-7c2e-6bc8-afcae32164c5@arm.com> (raw)
In-Reply-To: <20220120191250.2671557-2-pasha.tatashin@soleen.com>
On 1/21/22 12:42 AM, Pasha Tatashin wrote:
> The pte entry that is used in pte_advanced_tests() is never removed from
> the page table at the end of the test.
>
> The issue is detected by page_table_check, to repro compile kernel with
> the following configs:
>
> CONFIG_DEBUG_VM_PGTABLE=y
> CONFIG_PAGE_TABLE_CHECK=y
> CONFIG_PAGE_TABLE_CHECK_ENFORCED=y
Assuming this is on latest mainline.
I could enable PAGE_TABLE_CHECK on arm64 after some hacks. It did not build
on the platform otherwise. But enabling DEBUG_VM_PGTABLE afterwards did not
create below mentioned problems. Is the problem x86 specific ?
>
> During the boot the following BUG is printed:
>
> [ 7.483050][ T1] debug_vm_pgtable: [debug_vm_pgtable ]:
> Validating architecture page tabs
> [ 7.490930][ T1] ------------[ cut here ]------------
> [ 7.494926][ T1] kernel BUG at mm/page_table_check.c:194!
Which BUG() is this ? mm/page_table_check.c:194 on latest mainline ..
void __page_table_check_pud_clear(struct mm_struct *mm, unsigned long addr,
pud_t pud) <----
> [ 7.499172][ T1] invalid opcode: 0000 [#1] PREEMPT SMP KASAN
> [ 7.503610][ T1] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.16.0+
> [ 7.508600][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX,
> ...
>
> The entry should be properly removed from the page table before the page
> is released to the free list.
>
> Fixes: a5c3b9ffb0f4 ("mm/debug_vm_pgtable: add tests validating advanced arch page table helpers")
I am not sure whether this really fixes an existing problem.
>
> Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
> Reviewed-by: Zi Yan <ziy@nvidia.com>
> Tested-by: Zi Yan <ziy@nvidia.com>
> ---
> mm/debug_vm_pgtable.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/debug_vm_pgtable.c b/mm/debug_vm_pgtable.c
> index a7ac97c76762..db2abd9e415b 100644
> --- a/mm/debug_vm_pgtable.c
> +++ b/mm/debug_vm_pgtable.c
> @@ -171,6 +171,8 @@ static void __init pte_advanced_tests(struct pgtable_debug_args *args)
> ptep_test_and_clear_young(args->vma, args->vaddr, args->ptep);
> pte = ptep_get(args->ptep);
> WARN_ON(pte_young(pte));
> +
> + ptep_get_and_clear_full(args->mm, args->vaddr, args->ptep, 1);
> }
Although I dont see any problem on arm64 after this change.
>
> static void __init pte_savedwrite_tests(struct pgtable_debug_args *args)
>
next prev parent reply other threads:[~2022-01-21 3:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 19:12 [PATCH v2 0/3] page table check fixes and cleanups Pasha Tatashin
2022-01-20 19:12 ` [PATCH v2 1/3] mm/debug_vm_pgtable: remove pte entry from the page table Pasha Tatashin
2022-01-21 3:37 ` Anshuman Khandual [this message]
2022-01-21 14:03 ` Pasha Tatashin
2022-01-20 19:12 ` [PATCH v2 2/3] mm/page_table_check: check entries at pud and pmd levels Pasha Tatashin
2022-01-20 19:19 ` Wei Xu
2022-01-21 19:32 ` Pasha Tatashin
2022-01-20 19:12 ` [PATCH v2 3/3] mm/page_table_check: use unsigned long for page counters Pasha Tatashin
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=406f41ab-5ed9-7c2e-6bc8-afcae32164c5@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=dave.hansen@linux.intel.com \
--cc=gthelen@google.com \
--cc=hpa@zytor.com \
--cc=hughd@google.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=pasha.tatashin@soleen.com \
--cc=pjt@google.com \
--cc=qydwhotmail@gmail.com \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=songmuchun@bytedance.com \
--cc=weixugc@google.com \
--cc=will@kernel.org \
--cc=ziy@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox