netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Olsson <Robert.Olsson@data.slu.se>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: <netdev@vger.kernel.org>, Robert Olsson <robert.olsson@its.uu.se>,
	davem@davemloft.net
Subject: [PATCH] net: Fix the fib trie iterator to work with a single entry routing tables
Date: Wed, 24 Jan 2007 22:43:30 +0100	[thread overview]
Message-ID: <17847.54018.72176.431127@robur.slu.se> (raw)
In-Reply-To: <m17ivc19na.fsf@ebiederm.dsl.xmission.com>



Hello!

Yes the case when the trie is just a single leaf got wrong with the iterator and your patchs
cures it. I think we have a similar problem with /proc/net/fib_trie

Cheers
							--ro

Signed-off-by: Robert Olsson <robert.olsson@its.uu.se>



Eric W. Biederman writes:
 > 
 > In a kernel with trie routing enabled I had a simple routing setup
 > with only a single route to the outside world and no default
 > route. "ip route table list main" showed my the route just fine but
 > /proc/net/route was an empty file.  What was going on?
 > 
 > Thinking it was a bug in something I did and I looked deeper.  Eventually
 > I setup a second route and everything looked correct, huh?  Finally I
 > realized that the it was just the iterator pair in fib_trie_get_first,
 > fib_trie_get_next just could not handle a routing table with a single entry.
 > 
 > So to save myself and others further confusion, here is a simple fix for
 > the fib proc iterator so it works even when there is only a single route
 > in a routing table.
 > 
 > Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
 > ---
 >  net/ipv4/fib_trie.c |   21 ++++++++++++++++-----
 >  1 files changed, 16 insertions(+), 5 deletions(-)
 > 
 > diff --git a/net/ipv4/fib_trie.c b/net/ipv4/fib_trie.c
 > index cfb249c..13307c0 100644
 > --- a/net/ipv4/fib_trie.c
 > +++ b/net/ipv4/fib_trie.c
 > @@ -1989,6 +1989,10 @@ static struct node *fib_trie_get_next(struct fib_trie_iter *iter)
 >  	unsigned cindex = iter->index;
 >  	struct tnode *p;
 >  
 > +	/* A single entry routing table */
 > +	if (!tn)
 > +		return NULL;
 > +
 >  	pr_debug("get_next iter={node=%p index=%d depth=%d}\n",
 >  		 iter->tnode, iter->index, iter->depth);
 >  rescan:
 > @@ -2037,11 +2041,18 @@ static struct node *fib_trie_get_first(struct fib_trie_iter *iter,
 >  	if(!iter)
 >  		return NULL;
 >  
 > -	if (n && IS_TNODE(n)) {
 > -		iter->tnode = (struct tnode *) n;
 > -		iter->trie = t;
 > -		iter->index = 0;
 > -		iter->depth = 1;
 > +	if (n) {
 > +		if (IS_TNODE(n)) {
 > +			iter->tnode = (struct tnode *) n;
 > +			iter->trie = t;
 > +			iter->index = 0;
 > +			iter->depth = 1;
 > +		} else {
 > +			iter->tnode = NULL;
 > +			iter->trie  = t;
 > +			iter->index = 0;
 > +			iter->depth = 0;
 > +		}
 >  		return n;
 >  	}
 >  	return NULL;
 > -- 
 > 1.4.4.1.g278f

  reply	other threads:[~2007-01-24 22:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24 19:56 [PATCH] net: Fix the fib trie iterator to work with a single entry routing tables Eric W. Biederman
2007-01-24 21:43 ` Robert Olsson [this message]
2007-01-24 22:42   ` David Miller
2007-01-25  2:11     ` Eric W. Biederman
2007-01-26 12:56     ` Robert Olsson
2007-01-26 15:42       ` Eric W. Biederman
2007-01-27  3:06         ` David 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=17847.54018.72176.431127@robur.slu.se \
    --to=robert.olsson@data.slu.se \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=netdev@vger.kernel.org \
    --cc=robert.olsson@its.uu.se \
    /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).