Re: oops in __release_sock() [2.0.35]

Michael L. Galbraith (mikeg@weiden.de)
Sun, 4 Oct 1998 07:40:33 +0200 (CEST)


On Sun, 4 Oct 1998, Michael L. Galbraith wrote:

> On Sat, 3 Oct 1998, Andrea Arcangeli wrote:
>
> > On Fri, 2 Oct 1998, Michael L. Galbraith wrote:
> >
> > >The test had been running for 6 hrs. at Oops time. I've restarted webtest,
> > >and it's running fine again.. will see if it repeats.
> >
> > I spent one hour trying to understand what is causing the Oops.
> >
> > The problem is that a sock is been just kfreed and reused from other
> > pieces of code at release_sock() time.
> >
> > It would be nice if you could reproduce the Oops with this additional
> > debugging code:
>
> It just oopsed again after 1.5 hrs.. no diagnostic printk though.
>
> -Mike

But, the oops is a little different this time, so I should send it in :)
Does this suggest a timer interrupt coming at a very bad time to you?

Unable to handle kernel paging request at virtual address fe696c3c
current->tss.cr3 = 00cad000, %cr3 = 00cad000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<0013f902>]
EFLAGS: 00010206
eax: 00b8c89c ebx: 00b8c810 ecx: 3e696c3c edx: 0000002d
esi: 00b8c8d0 edi: 00b94f44 ebp: 00000000 esp: 00b94d08
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process webtest (pid: 223, process nr: 49, stackpage=00b94000)
Stack: 00b8c810 0014fa06 00b8c810 00b8c810 01072990 01072990 00000003 00978810
00bb4018 00000000 00000000 00000000 00000003 fc60fbe6 fc60fbe6 ca63fe76
ca63fe76 fc60fbe6 00000001 fc61795e ca63fe76 00000000 00000000 00000000
Call Trace: [<0014fa06>] [<00153340>] [<00155120>] [<00154da0>] [<00147e30>] [<0015ab20>] [<0015ab40>]
[<0015ab70>] [<0015ab20>] [<0015aff7>] [<0013d08c>] [<0013d305>] [<0012571c>] [<00125798>] [<001257f4>]
[<0010aa69>]
Code: 8b 11 8b 41 04 c7 01 00 00 00 00 c7 41 04 00 00 00 00 c7 41
Aiee, killing interrupt handler
Using `/boot/2.0.35/System.map' to map addresses to symbols.

>>EIP: 13f902 <__release_sock+32/90>
Trace: 14fa06 <tcp_close+276/2a0>
Trace: 153340 <tcp_send_partial>
Trace: 155120 <tcp_retransmit_timer>
Trace: 154da0 <tcp_delack_timer>
Trace: 147e30 <net_timer>
Trace: 15ab20 <def_callback1>
Trace: 15ab40 <def_callback2>
Trace: 15ab70 <def_callback3>
Trace: 15ab20 <def_callback1>
Trace: 15aff7 <inet_release+67/70>
Trace: 13d08c <sock_release+5c/a0>
Trace: 13d305 <sock_close+25/30>
Trace: 12571c <__fput+1c/40>
Trace: 125798 <close_fp+58/70>
Trace: 1257f4 <sys_close+44/50>
Trace: 10aa69 <system_call+55/7c>
Code: 13f902 <__release_sock+32/90>
Code: 13f902 <__release_sock+32/90> 8b 11 movl (%ecx),%edx
Code: 13f904 <__release_sock+34/90> 8b 41 04 movl 0x4(%ecx),%eax
Code: 13f907 <__release_sock+37/90> c7 01 00 00 00 movl $0x0,(%ecx)
Code: 13f913 <__release_sock+43/90> c7 41 04 00 00 movl $0x0,0x4(%ecx)

-
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/