Re: zlib bug

[Darren Reed <avalon@coombs.anu.edu.au>]

In some mail from Artur Grabowski, sie said:
[...]
> That depends on in which order you do the double free.
> 
> if it's:
> 
> x = malloc();
> free(x);
> free(x);
> 
> Then everything should be safe with phk malloc.
> 
> But if it's:
> 
> x = malloc();
> free(x);
> a = malloc();
> free(x);
> b = malloc();
> 
> no malloc implementation will catch that and you have a big risk that
> 'a' and 'b' will point to the same memory.
> 
> I don't know how bad it was in zlib.

What about ppp (deflate) in the kernel and the kernel malloc/free ?

Is /sys/net/zlib.c in need of patching ?

Darren