From: Bjorn Helgaas <helgaas@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: lorenzo.pieralisi@arm.com, robh@kernel.org, kw@linux.com,
bhelgaas@google.com, michal.simek@xilinx.com,
linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] PCI: xilinx-nwl: Simplify code and fix a memory leak
Date: Tue, 30 Nov 2021 10:55:45 -0600 [thread overview]
Message-ID: <20211130165545.GA2743072@bhelgaas> (raw)
In-Reply-To: <5483f10a44b06aad55728576d489adfa16c3be91.1636279388.git.christophe.jaillet@wanadoo.fr>
On Sun, Nov 07, 2021 at 11:04:43AM +0100, Christophe JAILLET wrote:
> Allocate space for 'bitmap' in 'struct nwl_msi' at build time instead of
> dynamically allocating the memory at runtime.
Definitely a good change. To be pedantic, I don't think this converts
the alloc to *build* time. It converts it to probe-time, when
nwl_pcie_probe() calls devm_pci_alloc_host_bridge().
> This simplifies code (especially error handling paths) and avoid some
> open-coded arithmetic in allocator arguments
>
> This also fixes a potential memory leak. The bitmap was never freed. It is
> now part of a managed resource.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> drivers/pci/controller/pcie-xilinx-nwl.c | 30 ++++++------------------
> 1 file changed, 7 insertions(+), 23 deletions(-)
>
> diff --git a/drivers/pci/controller/pcie-xilinx-nwl.c b/drivers/pci/controller/pcie-xilinx-nwl.c
> index a72b4f9a2b00..40d070e54ad2 100644
> --- a/drivers/pci/controller/pcie-xilinx-nwl.c
> +++ b/drivers/pci/controller/pcie-xilinx-nwl.c
> @@ -146,7 +146,7 @@
>
> struct nwl_msi { /* MSI information */
> struct irq_domain *msi_domain;
> - unsigned long *bitmap;
> + DECLARE_BITMAP(bitmap, INT_PCI_MSI_NR);
> struct irq_domain *dev_domain;
> struct mutex lock; /* protect bitmap variable */
> int irq_msi0;
> @@ -335,12 +335,10 @@ static void nwl_pcie_leg_handler(struct irq_desc *desc)
>
> static void nwl_pcie_handle_msi_irq(struct nwl_pcie *pcie, u32 status_reg)
> {
> - struct nwl_msi *msi;
> + struct nwl_msi *msi = &pcie->msi;
> unsigned long status;
> u32 bit;
>
> - msi = &pcie->msi;
> -
> while ((status = nwl_bridge_readl(pcie, status_reg)) != 0) {
> for_each_set_bit(bit, &status, 32) {
> nwl_bridge_writel(pcie, 1 << bit, status_reg);
> @@ -560,30 +558,21 @@ static int nwl_pcie_enable_msi(struct nwl_pcie *pcie)
> struct nwl_msi *msi = &pcie->msi;
> unsigned long base;
> int ret;
> - int size = BITS_TO_LONGS(INT_PCI_MSI_NR) * sizeof(long);
>
> mutex_init(&msi->lock);
>
> - msi->bitmap = kzalloc(size, GFP_KERNEL);
> - if (!msi->bitmap)
> - return -ENOMEM;
> -
> /* Get msi_1 IRQ number */
> msi->irq_msi1 = platform_get_irq_byname(pdev, "msi1");
> - if (msi->irq_msi1 < 0) {
> - ret = -EINVAL;
> - goto err;
> - }
> + if (msi->irq_msi1 < 0)
> + return -EINVAL;
>
> irq_set_chained_handler_and_data(msi->irq_msi1,
> nwl_pcie_msi_handler_high, pcie);
>
> /* Get msi_0 IRQ number */
> msi->irq_msi0 = platform_get_irq_byname(pdev, "msi0");
> - if (msi->irq_msi0 < 0) {
> - ret = -EINVAL;
> - goto err;
> - }
> + if (msi->irq_msi0 < 0)
> + return -EINVAL;
>
> irq_set_chained_handler_and_data(msi->irq_msi0,
> nwl_pcie_msi_handler_low, pcie);
> @@ -592,8 +581,7 @@ static int nwl_pcie_enable_msi(struct nwl_pcie *pcie)
> ret = nwl_bridge_readl(pcie, I_MSII_CAPABILITIES) & MSII_PRESENT;
> if (!ret) {
> dev_err(dev, "MSI not present\n");
> - ret = -EIO;
> - goto err;
> + return -EIO;
> }
>
> /* Enable MSII */
> @@ -632,10 +620,6 @@ static int nwl_pcie_enable_msi(struct nwl_pcie *pcie)
> nwl_bridge_writel(pcie, MSGF_MSI_SR_LO_MASK, MSGF_MSI_MASK_LO);
>
> return 0;
> -err:
> - kfree(msi->bitmap);
> - msi->bitmap = NULL;
> - return ret;
> }
>
> static int nwl_pcie_bridge_init(struct nwl_pcie *pcie)
> --
> 2.30.2
>
prev parent reply other threads:[~2021-11-30 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 10:04 [PATCH] PCI: xilinx-nwl: Simplify code and fix a memory leak Christophe JAILLET
2021-11-08 0:31 ` Krzysztof Wilczyński
2021-11-08 6:37 ` Christophe JAILLET
2021-11-29 13:41 ` Lorenzo Pieralisi
2021-11-30 16:55 ` Bjorn Helgaas [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=20211130165545.GA2743072@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=michal.simek@xilinx.com \
--cc=robh@kernel.org \
/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