From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Thorsten Blum <thorsten.blum@linux.dev>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Aditya Gupta <adityag@linux.ibm.com>,
Hari Bathini <hbathini@linux.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] powerpc/kexec: Annotate umem_info members with __counted_by_ptr
Date: Fri, 25 Sep 2026 11:49:04 +0530 [thread overview]
Message-ID: <7d99725f-9c90-48ca-bee1-30e2e6c06617@linux.ibm.com> (raw)
In-Reply-To: <20260730130248.597249-2-thorsten.blum@linux.dev>
On 30/07/26 18:32, Thorsten Blum wrote:
> Add __counted_by_ptr() to umem_info::buf and umem_info::ranges to
> improve access bounds checking via CONFIG_UBSAN_BOUNDS and
> CONFIG_FORTIFY_SOURCE.
>
> Set the count fields before assigning the corresponding pointers, return
> early on krealloc() failure, and use sizeof(*buf) when deriving
> max_entries from the allocation size.
>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
> arch/powerpc/kexec/file_load_64.c | 22 ++++++++++++----------
> 1 file changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/arch/powerpc/kexec/file_load_64.c b/arch/powerpc/kexec/file_load_64.c
> index 8c72e12ea44e..6424b668f0e9 100644
> --- a/arch/powerpc/kexec/file_load_64.c
> +++ b/arch/powerpc/kexec/file_load_64.c
> @@ -34,14 +34,15 @@
> #include <asm/cputhreads.h>
>
> struct umem_info {
> - __be64 *buf; /* data buffer for usable-memory property */
> + /* data buffer for usable-memory property */
> + __be64 *buf __counted_by_ptr(max_entries);
> u32 size; /* size allocated for the data buffer */
> u32 max_entries; /* maximum no. of entries */
> u32 idx; /* index of current entry */
>
> /* usable memory ranges to look up */
> unsigned int nr_ranges;
> - const struct range *ranges;
> + const struct range *ranges __counted_by_ptr(nr_ranges);
> };
[...]
>
> const struct kexec_file_ops * const kexec_file_loaders[] = {
> @@ -83,11 +84,12 @@ static __be64 *check_realloc_usable_mem(struct umem_info *um_info, int cnt)
>
> new_size = um_info->size + MEM_RANGE_CHUNK_SZ;
> tbuf = krealloc(um_info->buf, new_size, GFP_KERNEL);
> - if (tbuf) {
> - um_info->buf = tbuf;
> - um_info->size = new_size;
> - um_info->max_entries = (um_info->size / sizeof(u64));
> - }
> + if (!tbuf)
> + return NULL;
> +
> + um_info->size = new_size;
> + um_info->max_entries = um_info->size / sizeof(*um_info->buf);
> + um_info->buf = tbuf;
Could you please explain why size and max_entries are updated before the
buffer itself?
- Sourabh Jain
>
> return tbuf;
> }
> @@ -288,13 +290,13 @@ static int update_usable_mem_fdt(void *fdt, struct crash_mem *usable_mem)
> return -EINVAL;
> }
>
> - um_info.buf = NULL;
> um_info.size = 0;
> um_info.max_entries = 0;
> - um_info.idx = 0;
> + um_info.buf = NULL;
> + um_info.idx = 0;
> /* Memory ranges to look up */
> - um_info.ranges = &(usable_mem->ranges[0]);
> um_info.nr_ranges = usable_mem->nr_ranges;
> + um_info.ranges = usable_mem->ranges;
>
> dn = of_find_node_by_path("/ibm,dynamic-reconfiguration-memory");
> if (dn) {
>
prev parent reply other threads:[~2026-09-25 6:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 13:02 Thorsten Blum
2026-09-25 6:19 ` Sourabh Jain [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=7d99725f-9c90-48ca-bee1-30e2e6c06617@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=adityag@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=gustavoars@kernel.org \
--cc=hbathini@linux.ibm.com \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=thorsten.blum@linux.dev \
/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
all inboxes | Powered by JetHome®