From patchwork Fri Jun 17 20:36:33 2011 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Eric Dumazet X-Patchwork-Id: 100858 X-Patchwork-Delegate: davem@davemloft.net Return-Path: X-Original-To: patchwork-incoming@ozlabs.org Delivered-To: patchwork-incoming@ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id B4E6AB6F6E for ; Sat, 18 Jun 2011 06:36:49 +1000 (EST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932703Ab1FQUgk (ORCPT ); Fri, 17 Jun 2011 16:36:40 -0400 Received: from mail-wy0-f174.google.com ([74.125.82.174]:61318 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932321Ab1FQUgh (ORCPT ); Fri, 17 Jun 2011 16:36:37 -0400 Received: by wyb38 with SMTP id 38so562828wyb.19 for ; Fri, 17 Jun 2011 13:36:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:cc:in-reply-to:references :content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=cKVlMaEChRypL1Sk15AJRWc2538jNYiPQUfQzdaa6JY=; b=h0mmSKDqPTCyRA72CP96iLgdXfw+mqaCyW93mRtNZR9lkBDXi5kdHZTpVVhQD6ycf4 7pkVKifDdzGCmDzgiK3+qCjijU7efryGyQmX8iOk3ynzT+JjH6n6TaPcNcTrYX7WTsSB XWOAEUZ7GRbvbUj7GwXMuPLDMohDzrZi2ajoE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=N/zwcjyoA0XAqFUn+kqnJInj2X0QKcYcJCiZqEqd7DqFbvFuS7cgXihTzpQGD5rmKF 6yfgWa1irnFckORDFtbmRrK3laHXTnq9U9naC8F57vvSsHLDNZXIt7HX2mBYGFrrkZMT z3RVGg6975vuL5Y1tzZI7CuugPWXFTDm+9TdM= Received: by 10.227.104.2 with SMTP id m2mr2548347wbo.35.1308342996267; Fri, 17 Jun 2011 13:36:36 -0700 (PDT) Received: from [10.150.51.218] (gw0.net.jmsp.net [212.23.165.14]) by mx.google.com with ESMTPS id gb6sm1223709wbb.51.2011.06.17.13.36.35 (version=SSLv3 cipher=OTHER); Fri, 17 Jun 2011 13:36:35 -0700 (PDT) Subject: Re: what's causing "ip_rt_bug"? From: Eric Dumazet To: Tomasz Chmielewski Cc: netdev@vger.kernel.org In-Reply-To: <4DFBB270.8000003@wpkg.org> References: <4DFBB270.8000003@wpkg.org> Date: Fri, 17 Jun 2011 22:36:33 +0200 Message-ID: <1308342993.3539.30.camel@edumazet-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Le vendredi 17 juin 2011 à 22:00 +0200, Tomasz Chmielewski a écrit : > I have a system pushing around 800 Mbit/s, ~130 kpps. > > It uses 2.6.35.12 kernel. > > > Several times a minute, I can see entries like (a.b.c.d - IP of this system): > > Jun 18 02:39:19 KOR-SV22 kernel: [37187.665951] ip_rt_bug: 110.x.x.x -> a.b.c.d, ? > Jun 18 02:39:19 KOR-SV22 kernel: [37187.685419] ip_rt_bug: 110.x.x.x -> a.b.c.d, ? > Jun 18 02:40:31 KOR-SV22 kernel: [37259.199315] ip_rt_bug: 124.x.x.x -> a.b.c.d, ? > Jun 18 02:40:36 KOR-SV22 kernel: [37263.828000] ip_rt_bug: 124.x.x.x -> a.b.c.d, ? > Jun 18 02:44:16 KOR-SV22 kernel: [37484.120689] ip_rt_bug: 110.x.x.x -> a.b.c.d, ? > Jun 18 02:44:19 KOR-SV22 kernel: [37487.114357] ip_rt_bug: 110.x.x.x -> a.b.c.d, ? > Hi What your routing table looks like ? (ip ro) You also could backport this patch so that we can catch where/why this happens commit c378a9c019cf5e017d1ed24954b54fae7bebd2bc Author: Dave Jones Date: Sat May 21 07:16:42 2011 +0000 ipv4: Give backtrace in ip_rt_bug(). Add a stack backtrace to the ip_rt_bug path for debugging Signed-off-by: Dave Jones Signed-off-by: David S. Miller --- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/net/ipv4/route.c b/net/ipv4/route.c index b24d58e..52b0b95 100644 --- a/net/ipv4/route.c +++ b/net/ipv4/route.c @@ -1665,6 +1665,7 @@ static int ip_rt_bug(struct sk_buff *skb) &ip_hdr(skb)->saddr, &ip_hdr(skb)->daddr, skb->dev ? skb->dev->name : "?"); kfree_skb(skb); + WARN_ON(1); return 0; }