Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751968Ab3FRFx7 (ORCPT ); Tue, 18 Jun 2013 01:53:59 -0400 Received: from mail-ee0-f54.google.com ([74.125.83.54]:35193 "EHLO mail-ee0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751000Ab3FRFx5 (ORCPT ); Tue, 18 Jun 2013 01:53:57 -0400 Message-ID: <1371534832.3252.206.camel@edumazet-glaptop> Subject: Re: [PATCH] tcp: Modify the condition for the first skb to collapse From: Eric Dumazet To: Jun Chen Cc: ycheng@google.com, ncardwell@google.com, edumazet@google.com, netdev@vger.kernel.org, Linux Kernel Date: Mon, 17 Jun 2013 22:53:52 -0700 In-Reply-To: <1371549179.28418.28.camel@chenjun-workstation> References: <1371478739.10495.5.camel@chenjun-workstation> <1371456935.3252.177.camel@edumazet-glaptop> <1371490190.28418.6.camel@chenjun-workstation> <1371464962.3252.181.camel@edumazet-glaptop> <1371495133.28418.19.camel@chenjun-workstation> <1371475281.3252.198.camel@edumazet-glaptop> <1371549179.28418.28.camel@chenjun-workstation> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2215 Lines: 72 On Tue, 2013-06-18 at 05:52 -0400, Jun Chen wrote: > > > There are many warning for tcp_recvmsg before this crash. I can't find > other memory warning in the logs, but I'm not sure whether there are > memory issues because of the length limitation of saved logs. I think > this logs will give you more information. > > <4>[ 7736.343742] ------------[ cut here ]------------ > > <4>[ 7736.343759] WARNING: > at /data/buildbot/workdir/jb/kernel/net/ipv4/tcp.c:1496 tcp_recvmsg > +0x3bf/0x910() > > <4>[ 7736.343775] recvmsg bug: copied AB57C870 seq AB57CD95 rcvnxt > AB57F19F fl 0 > > <4>[ 7736.343845] Call Trace: > > <4>[ 7736.343865] [] warn_slowpath_common+0x72/0xa0 > > <4>[ 7736.343888] [] ? tcp_recvmsg+0x3bf/0x910 > > <4>[ 7736.343902] [] ? tcp_recvmsg+0x3bf/0x910 > > <4>[ 7736.343922] [] warn_slowpath_fmt+0x33/0x40 > > <4>[ 7736.343944] [] tcp_recvmsg+0x3bf/0x910 > > <4>[ 7736.343968] [] inet_recvmsg+0x85/0xa0 > > <4>[ 7736.343992] [] sock_aio_read+0x140/0x160 > > <4>[ 7736.344016] [] ? set_next_entity+0xc1/0xf0 > > <4>[ 7736.344039] [] do_sync_read+0xb7/0xf0 > > <4>[ 7736.344064] [] ? rw_verify_area+0x6c/0x120 > > <4>[ 7736.344077] [] ? sys_epoll_wait+0x68/0x360 > > <4>[ 7736.344098] [] vfs_read+0x149/0x160 > > <4>[ 7736.344120] [] ? fget_light+0x58/0xd0 > > <4>[ 7736.344142] [] sys_read+0x3d/0x70 > > <4>[ 7736.344164] [] syscall_call+0x7/0xb > > <4>[ 7736.344187] [] ? perf_cpu_notify+0x45/0x89 > > <4>[ 7736.344205] ---[ end trace b3c5b245ce7ff5b5 ]--- > Thats exactly the interesting stuff ;) This was fixed, or should be fixed if still happening on more recent kernels. Basically, once we are in this state, there is nothing we can do to prevent a crash. Please try to reproduce the issue using 3.9 or David trees (net-next or net ) Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/