Skip to contentSkip to conversation

assertion (newsk->state != TCP_SYN_RECV)

DISCUSSION Ross Vandegrift 3 participants 4 messages Mar 12, 2003 – Mar 18, 2003

lore
Share & tools
lore
#0 lore raw

I've recently noticed these messages bouncing up in my logs every now and again. It's always with a particular machine, one that runs 2.4.20.

Google turns up one other post, made on Mon Jan 13
(http://hypermail.idiosynkrasia.net/linux-kernel/archived/2003/week02/0308.html)
but no responses or explanations followed.

Any word on what this means or if it's a problem?

Mar 11 12:56:51 ash kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) 
Mar 11 12:56:51 ash kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) 
Mar 11 12:56:51 ash kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) 
Mar 11 12:56:51 ash kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) 
Mar 11 12:56:51 ash kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) 
Mar 11 12:56:51 ash kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) 
Mar 11 12:57:01 ash kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) 
Mar 11 12:57:01 ash kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) 
Mar 11 12:57:01 ash kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) 
Mar 11 12:57:01 ash kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) 
Mar 11 12:57:01 ash kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229) 
Mar 11 12:57:01 ash kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689) 
Signature · 10 lines
Ross Vandegrift
[email protected]

A Pope has a Water Cannon.                               It is a Water Cannon.
He fires Holy-Water from it.                        It is a Holy-Water Cannon.
He Blesses it.                                 It is a Holy Holy-Water Cannon.
He Blesses the Hell out of it.          It is a Wholly Holy Holy-Water Cannon.
He has it pierced.                It is a Holey Wholly Holy Holy-Water Cannon.
He makes it official.       It is a Canon Holey Wholly Holy Holy-Water Cannon.
Batman and Robin arrive.                                       He shoots them.
#2 lore raw
Quoted 10 lines · you [David S. Miller]
Quoted 6 lines · Ross Vandegrift

I've recently noticed these messages bouncing up in my logs every now and again. It's always with a particular machine, one that runs 2.4.20.

Google turns up one other post, made on Mon Jan 13
(http://hypermail.idiosynkrasia.net/linux-kernel/archived/2003/week02/0308.html)
but no responses or explanations followed.

Try searching harder, it's a kernel bug which is fixed in current 2.4.21 prepatches.

For reference, the patch is at

http://marc.theaimsgroup.com/?l=linux-kernel&m=104399842612703&w=2

BTW: How severe is the bug? Is it a harmless message, or can it do bad things?

-- v --

[email protected]

#3 lore raw

From: Ville Herva <[email protected]>
Date: Tue, 18 Mar 2003 08:42:58 +0200

Quoted 2 lines · you [David S. Miller]

Try searching harder, it's a kernel bug which is fixed in current 2.4.21 prepatches.

For reference, the patch is at

http://marc.theaimsgroup.com/?l=linux-kernel&m=104399842612703&w=2

BTW: How severe is the bug? Is it a harmless message, or can it do bad things?

We believe that someone could take advantage of it to make a server get stuck. So I'd say it's serious.