From: Patrick McHardy <kaber@trash.net>
To: itkes@fat.imec.msu.ru
Cc: netdev@oss.sgi.com
Subject: Re: A bug in the Kernel?
Date: Sun, 27 Feb 2005 17:26:36 +0100 [thread overview]
Message-ID: <4221F4BC.1080409@trash.net> (raw)
In-Reply-To: <1125.80.249.146.137.1109520029.squirrel@mx.imec.msu.ru>
itkes@fat.imec.msu.ru wrote:
> Let us suppose the application to request the routing tabled dump. I heve
> found that in some conditions, this application may not receive some
> unchanged routes, if some other routes was deleted.
Could you describe this condition in more detail ? In your patch you
change the type of "args" to void *, which results in a bigger patch
and it shouldn't be done anyway. If you need to store a pointer simply
cast it to long. Please send a plain (not gzipped) patch without this
change and without the EXTRAVERSION change.
> P.S. After I have finished the patch, I found another bug in the Routing
> Tables Dump. In function fn_hash_dump_bucket in fib_hash.c there is a
> construction:
> if (i<s_i)
> continue;
> ...
> i++;
> If the first "if" is true in first moment, "i" will never be increased and
> some routes will be lost. My patch fixes this bug, too.
Good catch, this bug was introduced when switching to
hlist_for_each_entry().
- for (i=0; f; i++, f=f->fn_next) {
- if (i < s_i) continue;
+ i = 0;
+ hlist_for_each_entry(f, node, head, fn_hash) {
+ struct fib_alias *fa;
+
+ list_for_each_entry(fa, &f->fn_alias, fa_list) {
+ if (i < s_i)
+ continue;
Regards
Patrick
next prev parent reply other threads:[~2005-02-27 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 16:00 A bug in the Kernel? itkes
2005-02-27 16:26 ` Patrick McHardy [this message]
2005-02-27 19:33 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2005-03-11 11:27 itkes
2005-03-11 12:31 ` jamal
2005-03-18 17:44 itkes
2005-03-18 17:59 ` Stephen Hemminger
2005-04-12 12:31 itkes
2005-04-12 13:18 ` jamal
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=4221F4BC.1080409@trash.net \
--to=kaber@trash.net \
--cc=itkes@fat.imec.msu.ru \
--cc=netdev@oss.sgi.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.