From: Zenghui Yu <yuzenghui@huawei.com>
To: Guanrui Huang <guanrui.huang@linux.alibaba.com>
Cc: <maz@kernel.org>, <shannon.zhao@linux.alibaba.com>,
<tglx@linutronix.de>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] irqchip/gic-v3-its: Fix double free on error
Date: Fri, 12 Apr 2024 11:05:43 +0800 [thread overview]
Message-ID: <bed81abf-cc39-53f0-6b22-33a0c2678142@huawei.com> (raw)
In-Reply-To: <20240412021556.101792-1-guanrui.huang@linux.alibaba.com>
Hi Guanrui,
On 2024/4/12 10:15, Guanrui Huang wrote:
> In its_vpe_irq_domain_alloc, when its_vpe_init() returns an error
> with i > 0, its_vpe_irq_domain_free may free bitmap and vprop_page,
> and then there is a double free in its_vpe_irq_domain_alloc.
>
> Fix it by calling its_vpe_irq_domain_free directly, bitmap and
> vprop_page will be freed in this function.
>
> Signed-off-by: Guanrui Huang <guanrui.huang@linux.alibaba.com>
> ---
> drivers/irqchip/irq-gic-v3-its.c | 11 ++---------
> 1 file changed, 2 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
> index fca888b36680..55c83e19719d 100644
> --- a/drivers/irqchip/irq-gic-v3-its.c
> +++ b/drivers/irqchip/irq-gic-v3-its.c
> @@ -4521,8 +4521,6 @@ static int its_vpe_irq_domain_alloc(struct irq_domain *domain, unsigned int virq
> struct page *vprop_page;
> int base, nr_ids, i, err = 0;
>
> - BUG_ON(!vm);
> -
The BUG_ON() is indeed useless, though it'd be better to remove it in a
separate patch, with a commit message explaining why it is not needed.
> bitmap = its_lpi_alloc(roundup_pow_of_two(nr_irqs), &base, &nr_ids);
> if (!bitmap)
> return -ENOMEM;
> @@ -4561,13 +4559,8 @@ static int its_vpe_irq_domain_alloc(struct irq_domain *domain, unsigned int virq
> irqd_set_resend_when_in_progress(irq_get_irq_data(virq + i));
> }
>
> - if (err) {
> - if (i > 0)
> - its_vpe_irq_domain_free(domain, virq, i);
> -
> - its_lpi_free(bitmap, base, nr_ids);
> - its_free_prop_table(vprop_page);
> - }
> + if (err)
> + its_vpe_irq_domain_free(domain, virq, i);
This looks good,
Reviewed-by: Zenghui Yu <yuzenghui@huawei.com>
Thanks for the fix.
Zenghui
next prev parent reply other threads:[~2024-04-12 3:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 2:15 Guanrui Huang
2024-04-12 3:05 ` Zenghui Yu [this message]
2024-04-15 13:06 ` Markus Elfring
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=bed81abf-cc39-53f0-6b22-33a0c2678142@huawei.com \
--to=yuzenghui@huawei.com \
--cc=guanrui.huang@linux.alibaba.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=shannon.zhao@linux.alibaba.com \
--cc=tglx@linutronix.de \
/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®