| To: | toml@xxxxxxxxxx |
|---|---|
| Subject: | Re: IPSec: IPv6 random failures |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Thu, 22 May 2003 15:54:08 -0700 (PDT) |
| Cc: | netdev@xxxxxxxxxxx, kuznet@xxxxxxxxxxxxx |
| In-reply-to: | <OF5D0301D4.91C949F2-ON86256D2E.0061C9C3-86256D2E.006456C0@pok.ibm.com> |
| References: | <OF5D0301D4.91C949F2-ON86256D2E.0061C9C3-86256D2E.006456C0@pok.ibm.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: "Tom Lendacky" <toml@xxxxxxxxxx> 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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Route cache performance under stress, David S. Miller |
|---|---|
| Next by Date: | [PATCH] post-sysfs netdev cleanup, Jeff Muizelaar |
| Previous by Thread: | IPSec: IPv6 random failures, Tom Lendacky |
| Next by Thread: | Re: IPSec: IPv6 random failures, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |