> The problem is that a sock is been just kfreed and reused from other
> pieces of code at release_sock() time.
> sk->dead = 1;
> release_sock(sk);
Hi Andrea,
Aaargh. This problem is much worse than a "harmless __release_sock oops"
then. Before the oops is triggered in release_sock, the line
sk->dead = 1
has trashed some random kernel memory!!
Could explain a mysterious crash or two we've had :-) We see the
__release_sock oops every now and again.
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/