From: "David S. Miller" <davem@redhat.com>
To: toml@us.ibm.com
Cc: netdev@oss.sgi.com, kuznet@ms2.inr.ac.ru
Subject: Re: IPSec: IPv6 random failures
Date: Thu, 22 May 2003 15:54:08 -0700 (PDT) [thread overview]
Message-ID: <20030522.155408.85396915.davem@redhat.com> (raw)
In-Reply-To: <OF5D0301D4.91C949F2-ON86256D2E.0061C9C3-86256D2E.006456C0@pok.ibm.com>
From: "Tom Lendacky" <toml@us.ibm.com>
Date: Thu, 22 May 2003 13:15:58 -0500
It would seem that the flowi structure should use the actual IPv6
addresses instead of pointers to them, like the IPv4 section does.
Feedback?
Yes, precisely, thanks for spotting this. I introduced this
bug when I split out the policy flow cache into a generic spot.
I'll see how much work it is to change all of ipv6 to store
addresses directly into the flowi's instead of via pointers.
next prev parent reply other threads:[~2003-05-22 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 18:15 IPSec: IPv6 random failures Tom Lendacky
2003-05-22 22:54 ` David S. Miller [this message]
2003-05-23 0:43 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2003-05-23 15:42 Tom Lendacky
2003-05-23 20:50 ` 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=20030522.155408.85396915.davem@redhat.com \
--to=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--cc=toml@us.ibm.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).