You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is in WARN_ON(sk->sk_forward_alloc) in sk_stream_kill_queues() called from inet_csk_destroy_sock() which is called in turn from ss_do_close() of sync_socket. It seems we should call sock_rfree() for each freed skb which is linked with TCP socket.
My understanding is that sock_rfree()/sock_wfree() IS called automagically from kfree_skb() via skb->destructor. The only case it might not be called is when the SKB is shared and the memory is not actually released.
If HTTP parser returns TFW_BLOCK (bad HTTP message), then we get Oops:
The text was updated successfully, but these errors were encountered: