Herton - how about instrumenting a kernel with a 'WARN_ON(sk->sk_state != TCP_ESTABLISHED)' in the right place. Wouldn't that tell us the name of the offending thread ?
Herton - how about instrumenting a kernel with a 'WARN_ON( sk->sk_ state != TCP_ESTABLISHED)' in the right place. Wouldn't that tell us the name of the offending thread ?