From: "David S. Miller" <davem@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@oss.sgi.com, yoshfuji@linux-ipv6.org
Subject: Re: patches
Date: Thu, 29 Jul 2004 19:20:46 -0700 [thread overview]
Message-ID: <20040729192046.0a3fb71d.davem@redhat.com> (raw)
In-Reply-To: <20040730012431.GA21253@gondor.apana.org.au>
On Fri, 30 Jul 2004 11:24:31 +1000
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> Here is the routing headers patch again.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Applied.
Based upon reading of the rest of the thread about
this patch I understand that:
1) Direction checking suggested by Yoshifuji is unecessary
because on input segments_left will be zero in the type 0
routing header.
2) Both ipv4 and ipv6 erroneously do the xfrm route lookup
using the first hop destination not the final destination.
And this needs to be fixed with a followon patch.
Is this correct?
next prev parent reply other threads:[~2004-07-30 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 1:19 patches David S. Miller
2004-07-30 1:24 ` patches Herbert Xu
2004-07-30 2:20 ` David S. Miller [this message]
2004-07-30 2:22 ` patches Herbert Xu
2004-07-30 1:26 ` patches Herbert Xu
2004-07-30 2:30 ` patches 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=20040729192046.0a3fb71d.davem@redhat.com \
--to=davem@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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).