> In kernel 2.0.32 I have experienced a memory leak since 2.0.31. Which
> made me reboot my machines after two days of uptime. I finally found out
> that it was during backuptime that almost all memory was consumed. This
> can easely be reproduced by doing:
> cd /; tar clf - . | nc -w 1 somehost discard &
i have tried this script in various combinations, and route.c:1422 has
always ~10 allocations here :( Wondering whats the speciality in your
setup that triggers the bug.
> 24 route.c:1422
> 21277 route.c:1422
> 44965 route.c:1422
> 59828 route.c:1422
> 75578 route.c:1422
> 98298 route.c:1422
i have seen this bug once (not on my box), so we definitely have a
problem, we just have to reproduce it ... does enabling DEBUG_RT in
route.c show something weird?
> CONFIG_NET=y
> CONFIG_IP_FORWARD=y
> CONFIG_SYN_COOKIES=y
> CONFIG_IP_NOSR=y
> CONFIG_SKB_LARGE=y
> CONFIG_NETDEVICES=y
> CONFIG_DUMMY=y
hm, this is a router setup, will boot into such a kernel, but i dont think
i can reproduce a complex routing setup ...
> CONFIG_PPP=y
> CONFIG_SLIP=y
> CONFIG_SLIP_COMPRESSED=y
nc isnt going through these serial interfaces, right?
-- mingo