David S. Miller wrote:
It is better to implement this via backpointers in the debugging information, perhaps.
This appears to be the neighbour struct that holds the leaked reference: Sep 2 16:11:27 sb65g2 kernel: Leaked neighbor structure: Sep 2 16:11:27 sb65g2 kernel: next: 00000000 tbl: c03e82c0 parms: d8f78d80 dev: d63eec00 used: 34668 confirmed: 11117 updated: 26117 Sep 2 16:11:27 sb65g2 kernel: flags: 0x0 nud: 0x0 type: 1 dead: 1 probes: 6 hh: 00000000 refcnt: 1 Sep 2 16:11:27 sb65g2 kernel: output: c02ccae0 ops: c03e8260 It seems to have a refcnt, so maybe I just have to instrument ref counting for the neighbour struct as well... Ben
- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
-- Ben Greear <[EMAIL PROTECTED]> Candela Technologies Inc http://www.candelatech.com - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
