Re: [U-Boot-Users] Possible memory leak in cpu/ppc4xx/4xx_enet.c

Stefan Roese wrote: > On Saturday 15 March 2008, Dave Littell wrote: I looked around this message and it seems that ppc_4xx_eth_initialize() malloc()’s a EMAC_4XX_HW_PST structure and assigns it to dev->priv. However, nothing ever frees this buffer so standing on a ping will ult

Re: [U-Boot-Users] Possible memory leak in cpu/ppc4xx/4xx_enet.c

On Saturday 15 March 2008, Dave Littell wrote: > >> I looked around this message and it seems that ppc_4xx_eth_initialize() > >> malloc()’s a EMAC_4XX_HW_PST structure and assigns it to dev->priv. > >> However, nothing ever frees this buffer so standing on a ping will > >> ultimately pull down all

Re: [U-Boot-Users] Possible memory leak in cpu/ppc4xx/4xx_enet.c

Stefan Roese wrote: > Dave, > > On Saturday 15 March 2008, Dave Littell wrote: >> I've seen an issue with my 1.3.1-based port of U-Boot where a relatively >> large number of pings issued from the command line will ultimately fail >> with the message: >> >> Cannot allocate private hw data for eth_d

Re: [U-Boot-Users] Possible memory leak in cpu/ppc4xx/4xx_enet.c

Dave, On Saturday 15 March 2008, Dave Littell wrote: > I've seen an issue with my 1.3.1-based port of U-Boot where a relatively > large number of pings issued from the command line will ultimately fail > with the message: > > Cannot allocate private hw data for eth_device... > > I looked around th

[U-Boot-Users] Possible memory leak in cpu/ppc4xx/4xx_enet.c

Hi all, I've seen an issue with my 1.3.1-based port of U-Boot where a relatively large number of pings issued from the command line will ultimately fail with the message: Cannot allocate private hw data for eth_device... I looked around this message and it seems that ppc_4xx_eth_initialize() mal