[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6a468fb4-74b0-4bf3-49bc-cfc62d734e24@loongson.cn>
Date: Wed, 1 Jul 2020 17:23:29 +0800
From: Tiezhu Yang <yangtiezhu@...ngson.cn>
To: Markus Elfring <Markus.Elfring@....de>,
Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
Marc Zyngier <maz@...nel.org>, Guo Ren <guoren@...nel.org>,
linux-csky@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH v4 03/14] irqchip/csky-mpintc: Fix potential resource
leaks
On 07/01/2020 03:49 PM, Markus Elfring wrote:
>> exception handling. By the way, do some coding-style cleanups
> I propose to consider another bit of fine-tuning.
>
>
> …
>> +++ b/drivers/irqchip/irq-csky-mpintc.c
> …
>> @@ -270,12 +274,24 @@ csky_mpintc_init(struct device_node *node, struct device_node *parent)
>>
>> #ifdef CONFIG_SMP
>> ipi_irq = irq_create_mapping(root_domain, IPI_IRQ);
>> - if (!ipi_irq)
>> - return -EIO;
>> + if (!ipi_irq) {
>> + ret = -EIO;
>> + goto err_domain_remove;
> How do you think about to use the following source code variant
> at this place?
>
> + irq_domain_remove(root_domain);
> + ret = -EIO;
> + goto err_iounmap;
>
>
> Would you like to avoid the repetition of the check “#ifdef CONFIG_SMP”?
OK, thank you, it looks good to me, I will do it in v5.
>
> Regards,
> Markus
Powered by blists - more mailing lists