All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Sayali Patil <sayalip@linux.ibm.com>,
	linuxppc-dev@lists.ozlabs.org, maddy@linux.ibm.com,
	Christophe Leroy <chleroy@kernel.org>,
	Michael Ellerman <mpe@kernel.org>,
	Nicholas Piggin <npiggin@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Mahesh Salgaonkar <mahesh@linux.ibm.com>,
	Sourabh Jain <sourabhjain@linux.ibm.com>
Subject: Re: [PATCH v2] powerpc/fadump: define MIN_RMA in bytes value to fix overflow
Date: Mon, 15 Jun 2026 15:06:05 +0530	[thread overview]
Message-ID: <eci8du2i.ritesh.list@gmail.com> (raw)
In-Reply-To: <a9d56fe88218a7034296f1974568543a0ce2d973.1781265400.git.sayalip@linux.ibm.com>

Sayali Patil <sayalip@linux.ibm.com> writes:

> The MIN_RMA size checks in fadump_setup_param_area() use
> (MIN_RMA * 1024 * 1024), which is evaluated in int and can
> overflow when MIN_RMA is increased to values such as SZ_2G.
> This triggers compiler warnings such as:
>
> warning: integer overflow in expression of type 'int'
> results in '0' [-Woverflow]
>
> Define MIN_RMA directly in bytes using SZ_1M and update the
> callers accordingly. This avoids repeated unit conversions and
> prevents integer overflow.
>
> Also convert MIN_RMA back to MB when populating the firmware
> architecture vector, since firmware expects the value in MB.
>
> Fixes: b7bb46062457 ("powerpc/fadump: fix additional param memory reservation for HASH MMU")

Since this is not a bug per-se, so we need not add a Fixes tag.
But while we are at it, we may correct the commit subject to...

    powerpc/fadump: Define MIN_RMA in bytes rather than MB

... since there is no overflow with it's current value.

With the above changes in place, feel free to add:
Reviewed-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>


      reply	other threads:[~2026-06-15  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12 12:02 [PATCH v2] powerpc/fadump: define MIN_RMA in bytes value to fix overflow Sayali Patil
2026-06-15  9:36 ` Ritesh Harjani [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=eci8du2i.ritesh.list@gmail.com \
    --to=ritesh.list@gmail.com \
    --cc=chleroy@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mahesh@linux.ibm.com \
    --cc=mpe@kernel.org \
    --cc=npiggin@gmail.com \
    --cc=sayalip@linux.ibm.com \
    --cc=sourabhjain@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.