From: Markus Elfring <Markus.Elfring@web.de>
To: Guanrui Huang <guanrui.huang@linux.alibaba.com>,
linux-arm-kernel@lists.infradead.org,
kernel-janitors@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
Zenghui Yu <yuzenghui@huawei.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Shannon Zhao <shannon.zhao@linux.alibaba.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v5 1/2] irqchip/gic-v3-its: Fix double free on error
Date: Thu, 18 Apr 2024 09:55:29 +0200 [thread overview]
Message-ID: <dd8cb3dc-8ac8-408c-845d-af60307d72e4@web.de> (raw)
In-Reply-To: <20240418061053.96803-2-guanrui.huang@linux.alibaba.com>
I propose to improve the commit message another bit.
How do you think about to append the text “in its_vpe_irq_domain_alloc()”
to the summary phrase?
> 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.
Can it be nicer to avoid the duplicate specification of a function name
in this change description?
> Fix it by calling its_vpe_irq_domain_free directly, bitmap and
> vprop_page will be freed in this function.
* Can the phrase “Fix it by” be omitted for an other imperative wording variant?
* Would you like to separate sentences by a dot instead of combining them
with a comma?
Regards,
Markus
next prev parent reply other threads:[~2024-04-18 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 6:10 [PATCH v5 0/2] " Guanrui Huang
2024-04-18 6:10 ` [PATCH v5 1/2] " Guanrui Huang
2024-04-18 7:55 ` Markus Elfring [this message]
2024-04-25 12:46 ` [tip: irq/urgent] irqchip/gic-v3-its: Prevent " tip-bot2 for Guanrui Huang
2024-04-18 6:10 ` [PATCH v5 2/2] irqchip/gic-v3-its: remove BUG_ON in its_vpe_irq_domain_alloc Guanrui Huang
2024-04-18 6:56 ` Zenghui Yu
2024-04-25 12:46 ` [tip: irq/core] irqchip/gic-v3-its: Remove " tip-bot2 for Guanrui Huang
2024-04-18 7:18 ` [PATCH v5 0/2] irqchip/gic-v3-its: Fix double free on error Marc Zyngier
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=dd8cb3dc-8ac8-408c-845d-af60307d72e4@web.de \
--to=markus.elfring@web.de \
--cc=guanrui.huang@linux.alibaba.com \
--cc=kernel-janitors@vger.kernel.org \
--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 \
--cc=yuzenghui@huawei.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 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®