All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nam Cao <namcao@linutronix.de>
To: "Madhavan Srinivasan" <maddy@linux.ibm.com>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Nicholas Piggin" <npiggin@gmail.com>,
	"Christophe Leroy" <christophe.leroy@csgroup.eu>,
	"Gautam Menghani" <gautam@linux.ibm.com>,
	"Cédric Le Goater" <clg@kaod.org>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Nam Cao <namcao@linutronix.de>
Subject: [PATCH 0/2] powerpc: Fix integer underflow & leak
Date: Mon,  4 Aug 2025 12:07:26 +0200	[thread overview]
Message-ID: <cover.1754300646.git.namcao@linutronix.de> (raw)

Hi,

This series fixes integer overflow & leak problem. I noticed this problem
when Gautam reported a kernel bug with another patch series of mine:
https://lore.kernel.org/linuxppc-dev/aH9Na8ZqrI0jPhtl@li-c6426e4c-27cf-11b2-a85c-95d65bc0de0e.ibm.com/

The root cause of that report is a bug in that series. However, that bug
triggered another existing bug, causing the reported end results.

Nam Cao (2):
  powerpc/pseries/msi: Fix potential underflow and leak issue
  powerpc/powernv/pci: Fix underflow and leak issue

 arch/powerpc/platforms/powernv/pci-ioda.c | 2 +-
 arch/powerpc/platforms/pseries/msi.c      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

-- 
2.39.5



             reply	other threads:[~2025-08-04 10:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04 10:07 Nam Cao [this message]
2025-08-04 10:07 ` [PATCH 1/2] powerpc/pseries/msi: Fix potential underflow and leak issue Nam Cao
2025-08-04 10:18   ` Cédric Le Goater
2025-08-04 10:07 ` [PATCH 2/2] powerpc/powernv/pci: Fix " Nam Cao
2025-08-04 10:18   ` Cédric Le Goater
2025-09-06 10:07 ` [PATCH 0/2] powerpc: Fix integer underflow & leak Madhavan Srinivasan

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=cover.1754300646.git.namcao@linutronix.de \
    --to=namcao@linutronix.de \
    --cc=christophe.leroy@csgroup.eu \
    --cc=clg@kaod.org \
    --cc=gautam@linux.ibm.com \
    --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 \
    /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.