Netdev Archive on lore.kernel.org help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org> To: Steffen Klassert <steffen.klassert@secunet.com>, Herbert Xu <herbert@gondor.apana.org.au>, "David S. Miller" <davem@davemloft.net> Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: IPSec questions and comments Date: Fri, 23 Jul 2021 20:01:17 -0500 [thread overview] Message-ID: <20210724010117.GA633665@minyard.net> (raw) <herbert@gondor.apana.org.au>, "David S. Miller" <davem@davemloft.net> Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org Bcc: Subject: IPSec questions Reply-To: minyard@acm.org I've been going through the XFRM code trying to understand it. I've been documenting things in the code as I go. I have a specific usage question, then a general question: 1) In struct xfrm_dst, what is the difference between the route and path fields? From what I can tell, in the first element of a bundle they will both point the route the packet will take after it has been transformed. In the other elements of a bundle, route is the same as in the first element and path will be NULL. Is this really the intent? Can path just be eliminated? 2) This code is really hard to understand. Nobody should have to go through what I'm going through. If I can convince my employer to allow me to submit the comments I'm adding, would that be something acceptable? It would obviously take a lot of time to review. If nobody's going to have the time to review it, I don't need to put forth the extra effort to make it submittable. Thanks, -corey
next reply other threads:[~2021-07-24 1:01 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-24 1:01 Corey Minyard [this message] 2021-07-24 2:40 ` IPSec questions and comments Eyal Birger [not found] ` <91bce7da-163d-dee3-5309-ebcf27de1abb@gmail.com> 2021-07-24 6:15 ` question about configuring multiple interfaces on a host within the same ipv6 sub-net hui wang 2021-07-25 2:32 ` hui wang 2021-07-26 8:13 ` IPSec questions and comments Steffen Klassert
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=20210724010117.GA633665@minyard.net \ --to=minyard@acm.org \ --cc=davem@davemloft.net \ --cc=herbert@gondor.apana.org.au \ --cc=linux-kernel@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=steffen.klassert@secunet.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: linkBe 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).