All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Jyoti Gupta <jyoti@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	Christophe Leroy <chleroy@kernel.org>,
	Shrikanth Hegde <sshegde@linux.ibm.com>,
	Amit Machhiwal <amachhiw@linux.ibm.com>,
	Sourabh Jain <sourabhjain@linux.ibm.com>,
	Mukesh Kumar Chaurasiya <mkchauras@gmail.com>
Subject: Re: [PATCH v3] powerpc/mpic: Fix memory leak of mpic on error paths
Date: Tue, 06 Oct 2026 19:59:31 +0530	[thread overview]
Message-ID: <4ieysy0k.ritesh.list@gmail.com> (raw)
In-Reply-To: <20261006065945.391637-1-jyoti@linux.ibm.com>

Jyoti Gupta <jyoti@linux.ibm.com> writes:

> mpic_alloc() allocates struct mpic (and optionally the protected
> sources bitmap) but does not free them when mpic_setup_error_int() or
> irq_domain_create_linear() fails, leaking the memory.
>
> Free the bitmap and the mpic in the common error path before
> dropping the device node reference.
>
> Fixes: 996983b75ceb ("powerpc/mpic: Search for open-pic device-tree node if NULL")
> Signed-off-by: Jyoti Gupta <jyoti@linux.ibm.com>
> ---
>
> Changelog
> ===========
> v2->v3:
>  + Introduce 'err_free_mpic' unwind label to cleanly free mpic and mpic->protected
>  + Link to v2: https://lore.kernel.org/all/20260930180919.335930-1-jyoti@linux.ibm.com/ 
>  
> ---
> ---
> arch/powerpc/sysdev/mpic.c | 11 +++++------
>  1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/arch/powerpc/sysdev/mpic.c b/arch/powerpc/sysdev/mpic.c
> index 257886ec3f70..d799cf4da7bd 100644
> --- a/arch/powerpc/sysdev/mpic.c
> +++ b/arch/powerpc/sysdev/mpic.c
> @@ -1389,7 +1389,7 @@ struct mpic * __init mpic_alloc(struct device_node *node,
>  		if (fsl_version >= 0x401) {
>  			ret = mpic_setup_error_int(mpic, intvec_top - 13);
>  			if (ret)
> -				return NULL;
> +				goto err_free_mpic;
>  		}
>  
>  	}
> @@ -1488,12 +1488,8 @@ struct mpic * __init mpic_alloc(struct device_node *node,
>  						 intvec_top,
>  						 &mpic_host_ops, mpic);
>  
> -	/*
> -	 * FIXME: The code leaks the MPIC object and mappings here; this
> -	 * is very unlikely to fail but it ought to be fixed anyways.
> -	 */

I don't think the current change fixes leaked mappings for
!CONFIG_PPC_DCR or !MPIC_USES_DCR. So removing this comment completely
doesn't look correct.
And maybe unless we have the HW or a way to really validate this - not
sure whether it is worth working on a full error handling routine to
unmap all the mappings from ioremap().

In that case, in this patch at-least, I think we should still keep this
comment i.e.:

/*
 * FIXME: The code leaks the MPIC mappings here; this is very unlikely
 * to fail but it ought to be fixed anyways.
 */

With that comment fixed - the change looks good to me, as it still fixes
the memory leak in error handling path. So feel free to add:

Reviewed-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>


>  	if (mpic->irqhost == NULL)
> -		return NULL;
> +		goto err_free_mpic;
>  
>  	/* Display version */
>  	switch (greg_feature & MPIC_GREG_FEATURE_VERSION_MASK) {
> @@ -1526,6 +1522,9 @@ struct mpic * __init mpic_alloc(struct device_node *node,
>  
>  	return mpic;
>  
> +err_free_mpic:
> +	bitmap_free(mpic->protected);
> +	kfree(mpic);
>  err_of_node_put:
>  	of_node_put(node);
>  	return NULL;
> -- 
> 2.55.0


      parent reply	other threads:[~2026-10-06 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06  6:59 [PATCH v3] powerpc/mpic: Fix memory leak of mpic on error paths Jyoti Gupta
2026-10-06  8:06 ` Mukesh Kumar Chaurasiya
2026-10-06  8:08 ` Amit Machhiwal
2026-10-06 14:29 ` 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=4ieysy0k.ritesh.list@gmail.com \
    --to=ritesh.list@gmail.com \
    --cc=amachhiw@linux.ibm.com \
    --cc=chleroy@kernel.org \
    --cc=jyoti@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mkchauras@gmail.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=sourabhjain@linux.ibm.com \
    --cc=sshegde@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.