Memory leaks in wpa_supplicant

Daniele C. legolas558 at users.sourceforge.net
Fri Mar 26 07:27:09 EDT 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello there,

I have enabled CONFIG_KMEMLEAK and I am finding some memory leakage apparently caused by wpa_supplicant

unreferenced object 0xcbdaf540 (size 64):
  comm "wpa_supplicant", pid 4035, jiffies 4294959545 (age 4171.613s)
  hex dump (first 32 bytes):
[ESSID STRING]
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xd1684e80 (size 64):
  comm "wpa_supplicant", pid 4035, jiffies 3381 (age 4160.481s)
  hex dump (first 32 bytes):
[ESSID STRING]
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xd1676c40 (size 64):
  comm "wpa_supplicant", pid 4941, jiffies 1420533 (age 2743.345s)
  hex dump (first 32 bytes):
[ESSID STRING]
  backtrace:
    [<ffffffff>] 0xffffffff
unreferenced object 0xd150fac0 (size 64):
  comm "wpa_supplicant", pid 5084, jiffies 1481828 (age 2682.050s)
  hex dump (first 32 bytes):
[ESSID STRING]
  backtrace:
    [<ffffffff>] 0xffffffff

The "[ESSID STRING]" was simply the 0-padded ESSID which I am connecting to; these leaks happen only the 1st time I start wpa_supplicant.

Is this a known memory leak bug?

Best regards,
- --
  Daniele C.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLrJoNAAoJEON28As9epPAzPsIAIQT/jSkZfAtlKbVmIR0aoQn
jQanv3QrZjyeKbvaLE7MteYV5mK+ipapuFfT2YEaFq2JRKB2o8jX820GGFdVaIc9
xftoEx057axTbOpWwKgORhCf6rkgLI5K/RiODdwUlRegDtH+SMyoY28WDHeESbIN
HGqSX6771TL7mzLe1rCOg5v9sPTfeR+QR49OKuSb0ySIlBbITcoglrUkizOk9GM0
bIkYNQHe2VNLdkCw+4ZKLNYugzcvV/+ry9MoCCvRaAjwsKU67vXo1+prcDuh3mYI
DNZPdM5rW2oObDuGL942WclKnwqVTERba5r70Qu7t2m1zwdmlGYFNIIglp7pI/0=
=Vzzq
-----END PGP SIGNATURE-----


More information about the HostAP mailing list