DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Li, WeiyuanX" <weiyuanx.li@intel.com>
To: "Laatz, Kevin" <kevin.laatz@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Laatz, Kevin" <kevin.laatz@intel.com>,
	"Morten Brørup" <mb@smartsharesystems.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: RE: [PATCH v2] bus: fix memleak during pci device cleanup
Date: Thu, 20 Oct 2022 05:31:59 +0000	[thread overview]
Message-ID: <CH3PR11MB7275B0BDC5B3BFDD6477ADC1E42A9@CH3PR11MB7275.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221019123743.1282969-1-kevin.laatz@intel.com>

> -----Original Message-----
> From: Kevin Laatz <kevin.laatz@intel.com>
> Sent: Wednesday, October 19, 2022 8:38 PM
> To: dev@dpdk.org
> Cc: Laatz, Kevin <kevin.laatz@intel.com>; Morten Brørup
> <mb@smartsharesystems.com>; Richardson, Bruce
> <bruce.richardson@intel.com>
> Subject: [PATCH v2] bus: fix memleak during pci device cleanup
> 
> During PCI bus device cleanup some interrupt handle pointers and the
> bus_info pointer are not being free'd, leading to memory leaks.
> This patch fixes the memory leaks by ensuring they are free'd during device
> cleanup on exit.
> 
> Fixes: 1cab1a40ea9b ("bus: cleanup devices on shutdown")
> 
> Signed-off-by: Kevin Laatz <kevin.laatz@intel.com>
> 
> ---
Tested-by: Weiyuan Li <weiyuanx.li@intel.com>

  reply	other threads:[~2022-10-20  5:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 10:49 [PATCH] " Kevin Laatz
2022-10-19 11:40 ` David Marchand
2022-10-19 12:37 ` [PATCH v2] " Kevin Laatz
2022-10-20  5:31   ` Li, WeiyuanX [this message]
2022-10-20  9:19   ` David Marchand
2022-10-20 11:31     ` David Marchand

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=CH3PR11MB7275B0BDC5B3BFDD6477ADC1E42A9@CH3PR11MB7275.namprd11.prod.outlook.com \
    --to=weiyuanx.li@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=kevin.laatz@intel.com \
    --cc=mb@smartsharesystems.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;
as well as URLs for NNTP newsgroup(s).