netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Flavio Leitner <fbl@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	Ivan Zahariev <famzah@icdsoft.com>,
	netdev@vger.kernel.org, Vasiliy Kulikov <segoon@openwall.com>
Subject: Re: Unable to flush ICMP redirect routes in kernel 3.0+
Date: Fri, 18 Nov 2011 15:05:12 -0200	[thread overview]
Message-ID: <20111118150512.5f66f7d2@asterix.rh> (raw)
In-Reply-To: <1321634046.3277.33.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>

On Fri, 18 Nov 2011 17:34:06 +0100
Eric Dumazet <eric.dumazet@gmail.com> wrote:

> Le vendredi 18 novembre 2011 à 14:30 -0200, Flavio Leitner a écrit :
> 
> > I know we are reverting to get it fixed, but this adds the routing
> > cache back, so what is the plan? Revert to get it working and then
> > think on new approach to remove the route cache again later?
> > 
> > I had one previous patch using the routing cache posted to the list,
> > but it won't fix the route flush problem.
> > 
> 
> I dont "add the routing cache back".

Sorry, I meant that we are trying to avoid doing this:
+			hash = rt_hash(daddr, skeys[s], ikeys[i],rt_genid(net));
+
+			rthp = &rt_hash_table[hash].chain;
+
+			while ((rt = rcu_dereference(*rthp)) != NULL) {
+				rthp = &rt->dst.rt_next;

anyway, see below.

> Note I only fix existing route entries in the cache ;)
Exactly.
 
> A "revert" is probably safe, since we should push a fix for
> 3.0/3.1/3.2 kernels...

I agree that reverting is probably safe.
fbl

  reply	other threads:[~2011-11-18 17:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15 20:23 Unable to flush ICMP redirect routes in kernel 3.0+ Ivan Zahariev
2011-11-15 21:09 ` Eric Dumazet
2011-11-16 22:32   ` Ivan Zahariev
2011-11-17  0:33     ` Flavio Leitner
2011-11-17  8:10       ` Ivan Zahariev
2011-11-17 13:11         ` Flavio Leitner
2011-11-17 13:15           ` Eric Dumazet
2011-11-17 14:40             ` Eric Dumazet
2011-11-17 15:37               ` Flavio Leitner
2011-11-17 16:31                 ` Eric Dumazet
2011-11-17 16:40                   ` Flavio Leitner
2011-11-17 16:45                     ` Eric Dumazet
2011-11-17 16:57                       ` Eric Dumazet
2011-11-17 17:01                       ` Flavio Leitner
2011-11-17 17:18                         ` Eric Dumazet
2011-11-17 17:33                           ` Flavio Leitner
2011-11-17 17:38                           ` Eric Dumazet
2011-11-18 16:02                             ` Eric Dumazet
2011-11-18 16:30                               ` Flavio Leitner
2011-11-18 16:34                                 ` Eric Dumazet
2011-11-18 17:05                                   ` Flavio Leitner [this message]
2011-11-18 17:07                                     ` Eric Dumazet
2011-11-18 17:21                                       ` Flavio Leitner
2011-11-18 18:04                                         ` David Miller
2011-11-18 20:26                               ` David Miller
2011-11-17 16:52               ` Vasiliy Kulikov

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=20111118150512.5f66f7d2@asterix.rh \
    --to=fbl@redhat.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=famzah@icdsoft.com \
    --cc=netdev@vger.kernel.org \
    --cc=segoon@openwall.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 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).