From: Patrick McHardy <kaber@trash.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: davem@davemloft.net, netdev@oss.sgi.com
Subject: Re: [PATCH 3/3 XFRM]: Fix invalid key for lookup of cached bundles
Date: Sun, 06 Mar 2005 11:54:07 +0100 [thread overview]
Message-ID: <422AE14F.6000805@trash.net> (raw)
In-Reply-To: <E1D7t0w-0008Qa-00@gondolin.me.apana.org.au>
Herbert Xu wrote:
> Patrick McHardy <kaber@trash.net> wrote:
>
>>@@ -97,6 +104,7 @@
>> err = xfrm_dst_lookup((struct xfrm_dst**)&rt, &fl_tunnel, AF_INET);
>> if (err)
>> goto error;
>>+ rt->u.dst.flags |= DST_XFRM_TUNNEL;
>
>
> This line doesn't look right. rt is an entry in the IPv4 routing
> cache, right? If so why should its flags change when some bundle is
> created?
>
> After all, it could also be used at the bottom of a transport mode bundle.
Oops, that is correct of course. I wanted to kill the ugly int
*is_tunnel argument to xfrm_bundle_ok() in my last patch, but
I need to look for a different way.
> Besides, I think IPv4 routing cache entry will never show up at the top of
> a bundle anyway which means that this flags value will never be read in
> the find_bundle function.
At least that part was correct, __xfrm4_find_bundle() uses
dst->path->flags in my patch.
Thanks,
Patrick
next prev parent reply other threads:[~2005-03-06 10:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 13:59 [PATCH 3/3 XFRM]: Fix invalid key for lookup of cached bundles Patrick McHardy
2005-03-06 10:29 ` Herbert Xu
2005-03-06 10:54 ` Patrick McHardy [this message]
2005-03-06 12:34 ` Patrick McHardy
2005-03-06 17:55 ` Patrick McHardy
2005-03-07 1:24 ` Herbert Xu
2005-03-07 1:41 ` Patrick McHardy
2005-03-07 1:43 ` Herbert Xu
2005-03-07 1:55 ` Patrick McHardy
2005-03-07 1:59 ` Herbert Xu
2005-03-07 2:30 ` Patrick McHardy
2005-03-07 2:57 ` Herbert Xu
2005-03-07 3:11 ` Patrick McHardy
2005-03-15 5:51 ` David S. Miller
2005-03-15 6:01 ` Herbert Xu
2005-03-15 6:14 ` 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=422AE14F.6000805@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@oss.sgi.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).