From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Li Zhijian <lizhijian@fujitsu.com>
Cc: <qemu-devel@nongnu.org>, Fan Ni <fan.ni@samsung.com>,
<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH 2/3] hw/mem/cxl_type3: Fix special_ops memory leak on msix_init_exclusive_bar() failure
Date: Tue, 21 Jan 2025 15:19:11 +0000 [thread overview]
Message-ID: <20250121151911.00002623@huawei.com> (raw)
In-Reply-To: <20250121145812.00004c63@huawei.com>
On Tue, 21 Jan 2025 14:58:12 +0000
Jonathan Cameron <Jonathan.Cameron@huawei.com> wrote:
> On Mon, 20 Jan 2025 11:09:46 +0800
> Li Zhijian <lizhijian@fujitsu.com> wrote:
>
> > Address a memory leak issue by ensuring `regs->special_ops` is freed when
> > `msix_init_exclusive_bar()` encounters an error during CXL Type3 device
> > initialization.
> >
> > Additionally, this patch renames err_address_space_free to err_msix_uninit
> > for better clarity and logical flow
> >
> > Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
> Hi.
>
> The need to reorder the cleanup calls made me look more
> closely at this patch. Either the order was wrong here or in the previous
> patch. I think the issue is here.
>
> Jonathan
>
> > ---
> > hw/mem/cxl_type3.c | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/hw/mem/cxl_type3.c b/hw/mem/cxl_type3.c
> > index 9dad250f56d5..9eb3d0979cf5 100644
> > --- a/hw/mem/cxl_type3.c
> > +++ b/hw/mem/cxl_type3.c
> > @@ -885,7 +885,7 @@ static void ct3_realize(PCIDevice *pci_dev, Error **errp)
> > /* MSI(-X) Initialization */
> > rc = msix_init_exclusive_bar(pci_dev, CXL_T3_MSIX_VECTOR_NR, 4, NULL);
> > if (rc) {
> > - goto err_address_space_free;
> > + goto err_free_special_ops;
> > }
> > for (i = 0; i < CXL_T3_MSIX_VECTOR_NR; i++) {
> > msix_vector_use(pci_dev, i);
> > @@ -899,7 +899,7 @@ static void ct3_realize(PCIDevice *pci_dev, Error **errp)
> > cxl_cstate->cdat.free_cdat_table = ct3_free_cdat_table;
> > cxl_cstate->cdat.private = ct3d;
> > if (!cxl_doe_cdat_init(cxl_cstate, errp)) {
> > - goto err_free_special_ops;
> > + goto err_msix_uninit;
> > }
> >
> > pcie_cap_deverr_init(pci_dev);
> > @@ -936,9 +936,9 @@ static void ct3_realize(PCIDevice *pci_dev, Error **errp)
> > err_release_cdat:
> > cxl_doe_cdat_release(cxl_cstate);
> > err_free_special_ops:
> > - msix_uninit_exclusive_bar(pci_dev);
> > g_free(regs->special_ops);
> > -err_address_space_free:
> > +err_msix_uninit:
> > + msix_uninit_exclusive_bar(pci_dev);
>
> This reorder doesn't look correct.
>
> Should end up I think as
> err_release_cdata:
> cxl_doe_cdata_release(cxl_cstate);
> err_msix_uninit:
> msix_uninit_eclusive_bar(pci_dev);
> err_free_special_ops:
> g_free(regs->special_ops)
> err_address_space_free:
This last label can go away.
I've applied your series with order modified as here to my CXL staging git
tree. I'll push out later today hopefully.
Thanks,
Jonathan
> etc.
>
> > if (ct3d->dc.host_dc) {
> > cxl_destroy_dc_regions(ct3d);
> > address_space_destroy(&ct3d->dc.host_dc_as);
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Li Zhijian <lizhijian@fujitsu.com>
Cc: <qemu-devel@nongnu.org>, Fan Ni <fan.ni@samsung.com>,
<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH 2/3] hw/mem/cxl_type3: Fix special_ops memory leak on msix_init_exclusive_bar() failure
Date: Tue, 21 Jan 2025 15:19:11 +0000 [thread overview]
Message-ID: <20250121151911.00002623@huawei.com> (raw)
In-Reply-To: <20250121145812.00004c63@huawei.com>
On Tue, 21 Jan 2025 14:58:12 +0000
Jonathan Cameron <Jonathan.Cameron@huawei.com> wrote:
> On Mon, 20 Jan 2025 11:09:46 +0800
> Li Zhijian <lizhijian@fujitsu.com> wrote:
>
> > Address a memory leak issue by ensuring `regs->special_ops` is freed when
> > `msix_init_exclusive_bar()` encounters an error during CXL Type3 device
> > initialization.
> >
> > Additionally, this patch renames err_address_space_free to err_msix_uninit
> > for better clarity and logical flow
> >
> > Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
> Hi.
>
> The need to reorder the cleanup calls made me look more
> closely at this patch. Either the order was wrong here or in the previous
> patch. I think the issue is here.
>
> Jonathan
>
> > ---
> > hw/mem/cxl_type3.c | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/hw/mem/cxl_type3.c b/hw/mem/cxl_type3.c
> > index 9dad250f56d5..9eb3d0979cf5 100644
> > --- a/hw/mem/cxl_type3.c
> > +++ b/hw/mem/cxl_type3.c
> > @@ -885,7 +885,7 @@ static void ct3_realize(PCIDevice *pci_dev, Error **errp)
> > /* MSI(-X) Initialization */
> > rc = msix_init_exclusive_bar(pci_dev, CXL_T3_MSIX_VECTOR_NR, 4, NULL);
> > if (rc) {
> > - goto err_address_space_free;
> > + goto err_free_special_ops;
> > }
> > for (i = 0; i < CXL_T3_MSIX_VECTOR_NR; i++) {
> > msix_vector_use(pci_dev, i);
> > @@ -899,7 +899,7 @@ static void ct3_realize(PCIDevice *pci_dev, Error **errp)
> > cxl_cstate->cdat.free_cdat_table = ct3_free_cdat_table;
> > cxl_cstate->cdat.private = ct3d;
> > if (!cxl_doe_cdat_init(cxl_cstate, errp)) {
> > - goto err_free_special_ops;
> > + goto err_msix_uninit;
> > }
> >
> > pcie_cap_deverr_init(pci_dev);
> > @@ -936,9 +936,9 @@ static void ct3_realize(PCIDevice *pci_dev, Error **errp)
> > err_release_cdat:
> > cxl_doe_cdat_release(cxl_cstate);
> > err_free_special_ops:
> > - msix_uninit_exclusive_bar(pci_dev);
> > g_free(regs->special_ops);
> > -err_address_space_free:
> > +err_msix_uninit:
> > + msix_uninit_exclusive_bar(pci_dev);
>
> This reorder doesn't look correct.
>
> Should end up I think as
> err_release_cdata:
> cxl_doe_cdata_release(cxl_cstate);
> err_msix_uninit:
> msix_uninit_eclusive_bar(pci_dev);
> err_free_special_ops:
> g_free(regs->special_ops)
> err_address_space_free:
This last label can go away.
I've applied your series with order modified as here to my CXL staging git
tree. I'll push out later today hopefully.
Thanks,
Jonathan
> etc.
>
> > if (ct3d->dc.host_dc) {
> > cxl_destroy_dc_regions(ct3d);
> > address_space_destroy(&ct3d->dc.host_dc_as);
>
>
next prev parent reply other threads:[~2025-01-21 15:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 3:09 [PATCH 1/3] hw/mem/cxl_type3: Add paired msix_uninit_exclusive_bar() call Li Zhijian
2025-01-20 3:09 ` Li Zhijian via
2025-01-20 3:09 ` [PATCH 2/3] hw/mem/cxl_type3: Fix special_ops memory leak on msix_init_exclusive_bar() failure Li Zhijian
2025-01-20 3:09 ` Li Zhijian via
2025-01-21 14:58 ` Jonathan Cameron
2025-01-21 14:58 ` Jonathan Cameron via
2025-01-21 15:19 ` Jonathan Cameron [this message]
2025-01-21 15:19 ` Jonathan Cameron via
2025-01-22 0:56 ` Zhijian Li (Fujitsu)
2025-01-22 0:56 ` Zhijian Li (Fujitsu) via
2025-01-20 3:09 ` [PATCH 3/3] hw/mem/cxl_type3: Ensure errp is set on realization failure Li Zhijian
2025-01-20 3:09 ` Li Zhijian via
2025-01-21 14:59 ` Jonathan Cameron
2025-01-21 14:59 ` Jonathan Cameron via
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=20250121151911.00002623@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=fan.ni@samsung.com \
--cc=linux-cxl@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=qemu-devel@nongnu.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 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.