From: Patrick McHardy <kaber@trash.net>
To: Michal Vanco <vanco@satro.sk>
Cc: netdev@oss.sgi.com, Andre Tomt <andre@tomt.net>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: 2.6.11 on AMD64 traps
Date: Wed, 09 Mar 2005 21:34:56 +0100 [thread overview]
Message-ID: <422F5DF0.6060904@trash.net> (raw)
In-Reply-To: <200503092124.35190.vanco@satro.sk>
Michal Vanco wrote:
> On Wednesday 09 March 2005 20:45, Patrick McHardy wrote:
>>
>>This patch should fix it. The crash is caused by stale pointers,
>>the pointers in fib_iter_state are not reloaded after seq->stop()
>>followed by seq->start(pos > 0).
>
> Well. Trap vanished after applying this patch, but another weird thing occurs:
>
> # ip route show | wc -l
> 156033
> # date; time ip route show > /dev/null; date; time netstat -rn > /dev/null
> Wed Mar 9 22:15:21 CET 2005
>
> real 0m0.656s
> user 0m0.415s
> sys 0m0.242s
> Wed Mar 9 22:15:22 CET 2005
>
> real 6m41.472s
> user 0m1.261s
> sys 6m40.143s
Yes, I know it is totally inefficient. Just use ip route, which doesn't
suffer from this problem.
Regards
Patrick
next prev parent reply other threads:[~2005-03-09 20:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200503081900.18686.vanco@satro.sk>
2005-03-08 18:35 ` 2.6.11 on AMD64 traps Andre Tomt
2005-03-09 19:45 ` Patrick McHardy
2005-03-09 20:24 ` Michal Vanco
2005-03-09 20:34 ` Patrick McHardy [this message]
2005-03-09 20:42 ` Michal Vanco
2005-03-09 21:05 ` Patrick McHardy
2005-03-09 21:17 ` Michal Vanco
2005-03-09 23:27 ` Patrick McHardy
2005-03-09 23:50 ` Michal Vanco
2005-03-09 23:57 ` Patrick McHardy
2005-03-10 0:43 ` David S. Miller
2005-03-11 2:20 ` David S. Miller
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=422F5DF0.6060904@trash.net \
--to=kaber@trash.net \
--cc=andre@tomt.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=vanco@satro.sk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).