Re: 2.0.33: Two ancient oopses in tcp_recvmsg

Camm Maguire (camm@enhanced.com)
25 Sep 1998 10:08:33 -0400


"David S. Miller" <davem@dm.cobaltmicro.com> writes:

> From: Florian Weimer <fw@cygnus.stuttgart.netsurf.de>
> Date: 24 Sep 1998 20:15:34 +0200
>
> I recently discovered the following oopses in the log file of a
> proxy server (486 with 8MB RAM, still running Linux 2.0.33). I
> suppose the bug has already been fixed and I'll install 2.0.35 as
> soon as possible, but I'd like to know what has caused these
> oopses.

(Florian's oops)

Aug 24 17:06:31 mail kernel: Unable to handle kernel NULL pointer dereference at virtual address c0000000
Aug 24 17:06:31 mail kernel: current->tss.cr3 = 00809000,
Aug 24 17:06:31 mail kernel: *pde = 00102067
Aug 24 17:06:31 mail kernel: *pte = 00000000
Aug 24 17:06:31 mail kernel: Oops: 0002
Aug 24 17:06:31 mail kernel: CPU: 0
Aug 24 17:06:32 mail kernel: EIP: 0010:[tcp_recvmsg+885/1120]
Aug 24 17:06:32 mail kernel: EFLAGS: 00010246
Aug 24 17:06:32 mail kernel: eax: 00000000 ebx: 002e0dfc ecx: 002f6c30 edx: 002f6ccc
Aug 24 17:06:32 mail kernel: esi: 000001a5 edi: 002fff78 ebp: 002f6c0c esp: 002ffee8
Aug 24 17:06:32 mail kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Aug 24 17:06:32 mail kernel: Process squid (pid: 16797, process nr: 32, stackpage=002ff000)
Aug 24 17:06:32 mail kernel: Stack: 002f6c0c 002fff7c 00000000 00000800 00000000 002f6c30 00000000 000001a5
Aug 24 17:06:32 mail kernel: 006cac0c 00768948 01c98848 001510d6 002f6c0c 002fff78 00000e5a 00000800
Aug 24 17:06:32 mail kernel: 00000000 002fff7c 00000fff 00768900 082f8360 00768990 00136c3b 00768990
Aug 24 17:06:33 mail kernel: Call Trace: [inet_recvmsg+118/144] [sock_read+171/208] [timer_bh+193/864] [sys_read+204/256] [system_call+85/124]
Aug 24 17:06:33 mail kernel: Code: 89 10 6a 01 53 89 4c 24 1c e8 2d 30 ff ff 83 c4 08 8b 4c 24

>
> It was a race in tcp_accept() which was fixed in 2.0.34 or 2.0.35
>

Greetings! This could be the case, but I'm still getting the
following with 2.0.35. These are udp, instead of tcp, packets,
though.

-----------------------------------------------------------------------------
Sep 15 06:30:02 intech12 kernel: Unable to handle kernel NULL pointer dereference at virtual address c0000008
Sep 15 06:30:02 intech12 kernel: current->tss.cr3 = 00943000, %cr3 = 00943000
Sep 15 06:30:02 intech12 kernel: *pde = 00102067
Sep 15 06:30:02 intech12 kernel: *pte = 00000000
Sep 15 06:30:02 intech12 kernel: Oops: 0000
Sep 15 06:30:02 intech12 kernel: CPU: 0
Sep 15 06:30:02 intech12 kernel: EIP: 0010:[memcpy_toiovec+82/144]
Sep 15 06:30:02 intech12 kernel: EFLAGS: 00010212
Sep 15 06:30:02 intech12 kernel: eax: 00001004 ebx: 00000190 ecx: 00000064 edx: bfffeae0
Sep 15 06:30:02 intech12 kernel: esi: 00000008 edi: bfffeae0 ebp: 00ea9edc esp: 00ea9e28
Sep 15 06:30:02 intech12 kernel: ds: 0018 es: 002b fs: 002b gs: 002b ss: 0018
Sep 15 06:30:02 intech12 kernel: Process pcqetix1 (pid: 4490, process nr: 25, stackpage=00ea9000)
Sep 15 06:30:02 intech12 kernel: Stack: 00040018 00000190 00ea9ee4 00044018 00ea9f64 00000190 0013bceb 00ea9edc
Sep 15 06:30:02 intech12 kernel: 00000008 00000190 0014ed91 00f0c5e4 00000008 00ea9edc 00000190 00044018
Sep 15 06:30:02 intech12 kernel: 00ea9ed8 00000000 00000000 00f0c5e4 0064c000 00153416 00044018 00ea9f64
Sep 15 06:30:02 intech12 kernel: Call Trace: [skb_copy_datagram_iovec+27/32] [udp_recvmsg+113/192] [inet_recvmsg+118/144] [sys_recvfrom+327/400] [udp_rcv+955/976] [ip_rcv+927/1248] [sys_socketcall+643/848]
Sep 15 06:30:02 intech12 kernel: [system_call+85/124]
Sep 15 06:30:02 intech12 kernel: Code: f3 a5 83 e3 03 89 d9 f3 a4 07 8b 5c 24 10 01 5c 24 1c 29 5c
-----------------------------------------------------------------------------

-- 
Camm Maguire			     			camm@enhanced.com
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

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