From: Flavio Leitner <fbl@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] route: fix ICMP redirect validation
Date: Fri, 21 Oct 2011 16:13:24 -0200 [thread overview]
Message-ID: <20111021161324.25916a7c@asterix.rh> (raw)
In-Reply-To: <20111020.161929.97626808571871075.davem@davemloft.net>
On Thu, 20 Oct 2011 16:19:29 -0400 (EDT)
David Miller <davem@davemloft.net> wrote:
> From: Flavio Leitner <fbl@redhat.com>
> Date: Thu, 20 Oct 2011 15:47:02 -0200
>
> > I was reviewing this again and instead of doing the above, it would
> > be better to use rt_bind_peer() to update rt->peer as well.
> >
> > if (!rt->peer)
> > rt_bind_peer(rt, rt->rt_dst, 1);
> >
> > peer = rt->peer;
> > if (peer) {
> > peer->redirect_learned.a4 = new_gw;
> > atomic_inc(&__rt_peer_genid);
> > }
> >
> >
> > but I am not sure if I understood you completely when you say
> > to do such that only an inetpeer cache probe is necessary.
>
> If you have the route entry available already and you're doing the
> inetpeer lookup anyways, you might as well use rt_bind_peer() since
> all of the expensive work has to be done anyways.
>
> So yes, using rt_bind_peer() would be the best thing to do here.
>
just posted patch v3. iirc, you prefer to receive patches as new
posts rather than replies to old threads.
"Subject: [PATCH net-next v3] route: fix ICMP redirect validation"
thanks again,
fbl
prev parent reply other threads:[~2011-10-21 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 14:20 [PATCH] route: fix ICMP redirect validation Flavio Leitner
2011-10-17 23:43 ` David Miller
2011-10-19 18:05 ` Flavio Leitner
2011-10-20 17:47 ` Flavio Leitner
2011-10-20 20:19 ` David Miller
2011-10-21 18:13 ` Flavio Leitner [this message]
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=20111021161324.25916a7c@asterix.rh \
--to=fbl@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).