> Subject: Re: [PATCH 1/3] bus/vmbus: fix leak on device scan
>
> On Thu, Sep 30, 2021 at 9:14 PM Long Li wrote:
> > > rte_device name only points at some location where the name is stored.
> > > In general this storage is in the bus object or (in some buses) the
> > > devarg that resulted in the
On Thu, Sep 30, 2021 at 9:14 PM Long Li wrote:
> > rte_device name only points at some location where the name is stored.
> > In general this storage is in the bus object or (in some buses) the devarg
> > that
> > resulted in the rte_device object creation.
> >
> > If we won't store the name in t
> Subject: Re: [PATCH 1/3] bus/vmbus: fix leak on device scan
>
> On Wed, Sep 29, 2021 at 10:57 PM Long Li wrote:
> >
> > > Subject: [PATCH 1/3] bus/vmbus: fix leak on device scan
> > >
> > > Caught running ASAN.
> > >
> > > The device name is leaked on scan.
> > > rte_device name field being a c
On Wed, Sep 29, 2021 at 10:57 PM Long Li wrote:
>
> > Subject: [PATCH 1/3] bus/vmbus: fix leak on device scan
> >
> > Caught running ASAN.
> >
> > The device name is leaked on scan.
> > rte_device name field being a const, use the private vmbus struct to store
> > the
> > device name and point at
> Subject: [PATCH 1/3] bus/vmbus: fix leak on device scan
>
> Caught running ASAN.
>
> The device name is leaked on scan.
> rte_device name field being a const, use the private vmbus struct to store the
> device name and point at it.
>
> Fixes: 831dba47bd36 ("bus/vmbus: add Hyper-V virtual bus s
Caught running ASAN.
The device name is leaked on scan.
rte_device name field being a const, use the private vmbus struct to
store the device name and point at it.
Fixes: 831dba47bd36 ("bus/vmbus: add Hyper-V virtual bus support")
Cc: sta...@dpdk.org
Signed-off-by: David Marchand
---
drivers/b
6 matches
Mail list logo
