All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: Stephen Hemminger <stephen.hemminger@vyatta.com>,
	netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: kernel 2.6.25-rc7 highly unstable on high load
Date: Fri, 28 Mar 2008 22:17:26 +0100	[thread overview]
Message-ID: <47ED6066.2010407@cosmosbay.com> (raw)
In-Reply-To: <20080328203358.M8487@visp.net.lb>

Denys Fedoryshchenko a écrit :
> It seems or patch change something (but it is just showing debug, strange), 
> or there is something fixed between 2.6.25-rc7-git1 and 2.6.25-rc7-git3. LC-
> trie working fine, HASH also i cannot see any leaks.

Yes, the fix is the patch we mentioned yesterday, and you told us you tried it :(

commit 7c0ecc4c4f8fd90988aab8a95297b9c0038b6160

[ICMP]: Dst entry leak in icmp_send host re-lookup code (v2).

Commit 8b7817f3a959ed99d7443afc12f78a7e1fcc2063 ([IPSEC]: Add ICMP host
relookup support) introduced some dst leaks on error paths: the rt
pointer can be forgotten to be put. Fix it bu going to a proper label.

Found after net namespace's lo refused to unregister :) Many thanks to
Den for valuable help during debugging.

Herbert pointed out, that xfrm_lookup() will put the rtable in case
of error itself, so the first goto fix is redundant.

Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
Signed-off-by: Denis V. Lunev <den@openvz.org>
Signed-off-by: David S. Miller <davem@davemloft.net>

> 
> I  will have to wait 5-6 hours to make sure. After this time pass, if i will 
> not see bug again, i will try to run kernel just with default debug like 
> before.
> 
> If it is required, i can test performance and cpu load with/without routing 
> cache on real workload. Sure it is better to have syntetic tests before that.


  reply	other threads:[~2008-03-28 21:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27  6:35 kernel 2.6.25-rc7 highly unstable on high load Denys Fedoryshchenko
2008-03-27  6:40 ` David Miller
2008-03-27  7:03   ` Eric Dumazet
2008-03-27  8:36     ` Denys Fedoryshchenko
2008-03-27  8:48     ` Denys Fedoryshchenko
2008-03-27 14:41     ` Denys Fedoryshchenko
2008-03-27 14:52       ` Eric Dumazet
     [not found]         ` <20080327151520.M89250@visp.net.lb>
2008-03-27 16:07           ` Eric Dumazet
2008-03-27 16:29             ` Eric Dumazet
2008-03-27 18:37             ` Denys Fedoryshchenko
2008-03-27 18:56               ` Eric Dumazet
2008-03-27 19:05                 ` Denis V. Lunev
2008-03-27 22:03                 ` David Miller
2008-03-28  0:47                   ` Denys Fedoryshchenko
2008-03-28  4:50                   ` Denys Fedoryshchenko
2008-03-28  5:25                   ` Denys Fedoryshchenko
2008-03-28  5:49                     ` Eric Dumazet
2008-03-28  7:38                       ` Denys Fedoryshchenko
2008-03-28  7:46                         ` Eric Dumazet
2008-03-28  9:50                           ` Denys Fedoryshchenko
2008-03-28 15:57                           ` Eric Dumazet
2008-03-28 20:23                             ` Stephen Hemminger
2008-03-28 20:45                               ` Denys Fedoryshchenko
2008-03-28 21:17                                 ` Eric Dumazet [this message]
2008-03-28 23:21                                   ` David Miller
2008-03-29  9:35                                     ` Denys Fedoryshchenko
     [not found]                                   ` <20080328220902.M5377@visp.net.lb>
2008-03-29  8:31                                     ` Eric Dumazet
2008-03-27  7:07   ` Denys Fedoryshchenko
2008-03-27 15:01   ` Patrick McHardy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47ED6066.2010407@cosmosbay.com \
    --to=dada1@cosmosbay.com \
    --cc=denys@visp.net.lb \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=stephen.hemminger@vyatta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.