From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>,
Linu Cherian <linu.cherian@arm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kasan-dev@googlegroups.com
Subject: Re: [RFC V1 07/16] arm64/mm: Convert READ_ONCE() as p4dp_get() while accessing P4D
Date: Wed, 15 Apr 2026 12:35:07 +0200 [thread overview]
Message-ID: <d61a8e11-5b8c-4cea-a7f4-a890f65d62f4@kernel.org> (raw)
In-Reply-To: <c490455f-084a-4f53-86b0-89c15669efb3@arm.com>
>>>
>>> @@ -2258,4 +2258,21 @@ int pmdp_test_and_clear_young(struct vm_area_struct *vma,
>>> }
>>> #endif /* CONFIG_TRANSPARENT_HUGEPAGE || CONFIG_ARCH_HAS_NONLEAF_PMD_YOUNG */
>>>
>>> +#if CONFIG_PGTABLE_LEVELS > 3
>>> +phys_addr_t pud_offset_phys(p4d_t *p4dp, unsigned long addr)
>>> +{
>>> + p4d_t p4d = p4dp_get(p4dp);
>>> +
>>> + BUG_ON(!pgtable_l4_enabled());
>>
>> Heh, while at it, convert that to a VM_WARN_ON_ONCE() or anything else
>> that is not a BUG.
>>
>> I strongly assume CONFIG_DEBUG_VM checks are sufficient.
>
> There are multiple similar BUG_ON() instances
>
> arch/arm64/include/asm/pgtable.h: BUG_ON(!pgtable_l4_enabled());
> arch/arm64/include/asm/pgtable.h: BUG_ON(!pgtable_l5_enabled());
>
> arch/arm64/mm/mmu.c: BUG_ON(pmd_val(old_pmd) != 0 &&
> arch/arm64/mm/mmu.c: BUG_ON(pud_val(old_pud) != 0 &&
> arch/arm64/mm/mmu.c: BUG_ON(p4d_val(old_p4d) != 0 &&
>
> Shall we convert all of them as VM_WARN_ON_ONCE() in a separate patch
> as a pre-requisite ?
In MM at least, we fix them up when touching the code, and only
sometimes convert entire files.
As documented in Documentation/process/coding-style.rst, there might be
some exceptions where BUG_ON makes sense (severe data corruption
possible), and some cases would want to use WARN_ON_ONCE() + recovery code.
All of these cases here sound like VM_WARN_ON_ONCE() is more than
sufficient though, so feel free to convert them all in one shot.
--
Cheers,
David
next prev parent reply other threads:[~2026-04-15 10:35 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 5:11 [RFC V1 00/16] arm64/mm: Enable 128 bit page table entries Anshuman Khandual
2026-02-24 5:11 ` [RFC V1 01/16] mm: Abstract printing of pxd_val() Anshuman Khandual
2026-02-26 12:34 ` Usama Arif
2026-02-26 12:49 ` Anshuman Khandual
2026-04-09 10:33 ` Mike Rapoport
2026-04-10 4:21 ` Anshuman Khandual
2026-02-24 5:11 ` [RFC V1 02/16] mm: Add read-write accessors for vm_page_prot Anshuman Khandual
2026-04-09 10:37 ` Mike Rapoport
2026-04-10 4:29 ` Anshuman Khandual
2026-02-24 5:11 ` [RFC V1 03/16] mm: Replace READ_ONCE() in pud_trans_unstable() Anshuman Khandual
2026-02-24 5:11 ` [RFC V1 04/16] perf/events: Replace READ_ONCE() with standard pgtable accessors Anshuman Khandual
2026-02-24 8:48 ` Peter Zijlstra
2026-02-24 10:08 ` Mark Rutland
2026-02-24 10:41 ` Peter Zijlstra
2026-02-24 11:22 ` Ryan Roberts
2026-02-24 12:49 ` Anshuman Khandual
2026-02-24 12:39 ` Anshuman Khandual
2026-02-24 12:53 ` Anshuman Khandual
2026-02-24 5:11 ` [RFC V1 05/16] arm64/mm: Convert READ_ONCE() as pmdp_get() while accessing PMD Anshuman Khandual
2026-04-08 12:11 ` David Hildenbrand (Arm)
2026-04-10 4:48 ` Anshuman Khandual
2026-04-15 10:31 ` David Hildenbrand (Arm)
2026-02-24 5:11 ` [RFC V1 06/16] arm64/mm: Convert READ_ONCE() as pudp_get() while accessing PUD Anshuman Khandual
2026-04-08 12:15 ` David Hildenbrand (Arm)
2026-04-10 4:50 ` Anshuman Khandual
2026-04-15 10:32 ` David Hildenbrand (Arm)
2026-02-24 5:11 ` [RFC V1 07/16] arm64/mm: Convert READ_ONCE() as p4dp_get() while accessing P4D Anshuman Khandual
2026-04-08 12:17 ` David Hildenbrand (Arm)
2026-04-10 5:05 ` Anshuman Khandual
2026-04-15 10:35 ` David Hildenbrand (Arm) [this message]
2026-02-24 5:11 ` [RFC V1 08/16] arm64/mm: Convert READ_ONCE() as pgdp_get() while accessing PGD Anshuman Khandual
2026-04-08 12:19 ` David Hildenbrand (Arm)
2026-04-10 5:30 ` Anshuman Khandual
2026-04-15 10:37 ` David Hildenbrand (Arm)
2026-02-24 5:11 ` [RFC V1 09/16] arm64/mm: Route all pgtable reads via ptdesc_get() Anshuman Khandual
2026-02-28 11:17 ` Mike Rapoport
2026-03-02 4:34 ` Anshuman Khandual
2026-04-08 12:25 ` David Hildenbrand (Arm)
2026-02-24 5:11 ` [RFC V1 10/16] arm64/mm: Route all pgtable writes via ptdesc_set() Anshuman Khandual
2026-02-26 12:37 ` Usama Arif
2026-02-26 12:54 ` Anshuman Khandual
2026-02-26 13:19 ` Ryan Roberts
2026-02-27 6:19 ` Anshuman Khandual
2026-02-24 5:11 ` [RFC V1 11/16] arm64/mm: Route all pgtable atomics to central helpers Anshuman Khandual
2026-04-08 12:28 ` David Hildenbrand (Arm)
2026-04-10 4:02 ` Anshuman Khandual
2026-04-15 10:38 ` David Hildenbrand (Arm)
2026-02-24 5:11 ` [RFC V1 12/16] arm64/mm: Abstract printing of pxd_val() Anshuman Khandual
2026-04-08 12:28 ` David Hildenbrand (Arm)
2026-04-10 4:05 ` Anshuman Khandual
2026-02-24 5:11 ` [RFC V1 13/16] arm64/mm: Override read-write accessors for vm_page_prot Anshuman Khandual
2026-02-24 5:11 ` [RFC V1 14/16] arm64/mm: Enable fixmap with 5 level page table Anshuman Khandual
2026-04-08 12:29 ` David Hildenbrand (Arm)
2026-04-10 3:22 ` Anshuman Khandual
2026-04-15 10:39 ` David Hildenbrand (Arm)
2026-02-24 5:11 ` [RFC V1 15/16] arm64/mm: Add macros __tlb_asid_level and __tlb_range Anshuman Khandual
2026-02-24 5:11 ` [RFC V1 16/16] arm64/mm: Add initial support for FEAT_D128 page tables Anshuman Khandual
2026-02-26 14:10 ` Usama Arif
2026-04-07 14:44 ` [RFC V1 00/16] arm64/mm: Enable 128 bit page table entries David Hildenbrand (Arm)
2026-04-08 10:53 ` Anshuman Khandual
2026-04-08 11:01 ` Ryan Roberts
2026-04-08 12:13 ` David Hildenbrand (Arm)
2026-04-09 2:08 ` Anshuman Khandual
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=d61a8e11-5b8c-4cea-a7f4-a890f65d62f4@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kasan-dev@googlegroups.com \
--cc=linu.cherian@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mark.rutland@arm.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=will@kernel.org \
/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