From: Steffen Klassert <steffen.klassert@secunet.com>
To: Corey Minyard <minyard@acm.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: Re: IPSec questions and comments
Date: Mon, 26 Jul 2021 10:13:50 +0200 [thread overview]
Message-ID: <20210726081350.GM893739@gauss3.secunet.de> (raw)
In-Reply-To: <20210724010117.GA633665@minyard.net>
On Fri, Jul 23, 2021 at 08:01:17PM -0500, Corey Minyard wrote:
> <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?
Eyal gave a good explanation of this.
>
> 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.
Documentation is always welcome. If you submit your documentation
in small reviewable patches, then it should be accepted and merged
over time.
prev parent reply other threads:[~2021-07-26 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 1:01 Corey Minyard
2021-07-24 2:40 ` Eyal Birger
2021-07-26 8:13 ` Steffen Klassert [this message]
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=20210726081350.GM893739@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®