From: Fan Du <fan.du@windriver.com>
To: <steffen.klassert@secunet.com>
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
davem@davemloft.net, dev@lists.strongswan.org
Subject: Re: [PATCH net-next 0/2] Pack struct xfrm_usersa_info and struct xfrm_userpolicy_info
Date: Tue, 7 Jan 2014 14:55:21 +0800 [thread overview]
Message-ID: <52CBA4D9.60806@windriver.com> (raw)
In-Reply-To: <1389077339-12814-1-git-send-email-fan.du@windriver.com>
Oh, I don't know why '[strongSwan-dev]' is tagged in front of subject for only part of whole patch set.
In fact, I didn't mean to add '[strongSwan-dev]' into subject line. Sorry for the inconvenience.
On 2014年01月07日 14:48, Fan Du wrote:
> When trying to setup IPsec configuration on a 64bits host with
> iproute2(32bits compiled), the intened xfrm policy and sa is
> either deficit or wrong when kernel trying to parse user land
> information.
>
> Further investigatino shows that:
> L: kernel
> R: iproute2
>
> sizeof userpolicy usersa
> 64bits(unpacked) 168/168 224/224
> 32bits(unpacked) 164/164 220/220
> ^ ^
> L R
>
> To keep kernel and user land see a consistent structure, after
> add packing attribute, now it looks like this:
>
> 64bits( packed) 164/164 217/217
> 32bits( packed) 164/164 217/217
> ^ ^
> L R
>
> Then different kernel/iproute2 build configuration will not impact IPsec setup.
>
> Fan Du (2):
> include/uapi/linux/xfrm.h: Pack struct xfrm_userpolicy_info
> include/uapi/linux/xfrm.h: Pack struct xfrm_usersa_info
>
> include/uapi/linux/xfrm.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
--
浮沉随浪只记今朝笑
--fan
_______________________________________________
Dev mailing list
Dev@lists.strongswan.org
https://lists.strongswan.org/mailman/listinfo/dev
next prev parent reply other threads:[~2014-01-07 6:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 6:48 [PATCH net-next 0/2] Pack struct xfrm_usersa_info and struct xfrm_userpolicy_info Fan Du
2014-01-07 6:48 ` [PATCH net-next 1/2] include/uapi/linux/xfrm.h: Pack " Fan Du
2014-01-07 22:52 ` Sergei Shtylyov
2014-01-09 8:39 ` Fan Du
2014-01-09 22:58 ` Sergei Shtylyov
2014-01-09 23:07 ` Sergei Shtylyov
2014-01-07 6:48 ` [PATCH net-next 2/2] include/uapi/linux/xfrm.h: Pack struct xfrm_usersa_info Fan Du
2014-01-08 20:33 ` Ben Hutchings
2014-01-09 8:24 ` Fan Du
2014-01-09 18:58 ` Ben Hutchings
2014-01-07 6:55 ` Fan Du [this message]
2014-01-07 7:47 ` [PATCH net-next 0/2] Pack struct xfrm_usersa_info and struct xfrm_userpolicy_info Steffen Klassert
2014-01-07 7:59 ` Fan Du
2014-01-07 10:00 ` David Laight
2014-01-09 8:34 ` Fan Du
2014-01-09 9:07 ` David Laight
2014-01-07 18:07 ` David Miller
2014-01-09 8:24 ` Fan Du
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=52CBA4D9.60806@windriver.com \
--to=fan.du@windriver.com \
--cc=davem@davemloft.net \
--cc=dev@lists.strongswan.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.