From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <ljs@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH V2 2/2] arm64/mm: Standardize printing for pgtable entries
Date: Wed, 9 Sep 2026 17:14:25 +0200 [thread overview]
Message-ID: <b058dbec-060b-4f19-8048-3951a32965a1@kernel.org> (raw)
In-Reply-To: <20260909040005.4148136-3-anshuman.khandual@arm.com>
> diff --git a/arch/arm64/mm/mmu.c b/arch/arm64/mm/mmu.c
> index 0b2d190d62c3..26f4cf7b753e 100644
> --- a/arch/arm64/mm/mmu.c
> +++ b/arch/arm64/mm/mmu.c
> @@ -2411,6 +2411,8 @@ int arch_set_user_pkey_access(int pkey, unsigned long init_val)
> #ifdef CONFIG_DEBUG_VM
> void __check_safe_pte_update(struct mm_struct *mm, pte_t *ptep, pte_t pte)
> {
> + char pte_str_old[PTVAL_STR_MAX];
> + char pte_str[PTVAL_STR_MAX];
Nothing jumped at me; once the stack usage does become a problem (I strongly
assume we don't care for now) we can revisit the approach of moving printing
into printk.
Reviewed-by: David Hildenbrand (Arm) <david@kernel.org>
--
Cheers,
David
prev parent reply other threads:[~2026-09-09 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 4:00 [PATCH V2 0/2] arm64/mm: Standardize printing for pgtable entries Anshuman Khandual
2026-09-09 4:00 ` [PATCH V2 1/2] arm64/mm: Move __check_safe_pte_update() Anshuman Khandual
2026-09-09 15:12 ` David Hildenbrand (Arm)
2026-09-10 4:05 ` Anshuman Khandual
2026-09-09 4:00 ` [PATCH V2 2/2] arm64/mm: Standardize printing for pgtable entries Anshuman Khandual
2026-09-09 15:14 ` David Hildenbrand (Arm) [this message]
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=b058dbec-060b-4f19-8048-3951a32965a1@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=rppt@kernel.org \
--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