From: David Miller <davem@davemloft.net>
To: steffen.klassert@secunet.com
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: pull request (net): ipsec 2015-03-16
Date: Mon, 16 Mar 2015 16:17:09 -0400 (EDT) [thread overview]
Message-ID: <20150316.161709.445020712639772193.davem@davemloft.net> (raw)
In-Reply-To: <1426488744-17104-1-git-send-email-steffen.klassert@secunet.com>
From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Mon, 16 Mar 2015 07:52:21 +0100
> 1) Fix the network header offset in _decode_session6
> when multiple IPv6 extension headers are present.
> From Hajime Tazaki.
>
> 2) Fix an interfamily tunnel crash. We set outer mode
> protocol too early and may dispatch to the wrong
> address family. Move the setting of the outer mode
> protocol behind the last accessing of the inner mode
> to fix the crash.
>
> 3) Most callers of xfrm_lookup() expect that dst_orig
> is released on error. But xfrm_lookup_route() may
> need dst_orig to handle certain error cases. So
> introduce a flag that tells what should be done in
> case of error. From Huaibin Wang.
>
> Please pull or let me know if there are problems.
Pulled, thanks a lot.
prev parent reply other threads:[~2015-03-16 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 6:52 pull request (net): ipsec 2015-03-16 Steffen Klassert
2015-03-16 6:52 ` [PATCH 1/3] xfrm6: Fix a offset value for network header in _decode_session6 Steffen Klassert
2015-03-16 6:52 ` [PATCH 2/3] xfrm: Fix local error reporting crash with interfamily tunnels Steffen Klassert
2015-03-16 6:52 ` [PATCH 3/3] xfrm: release dst_orig in case of error in xfrm_lookup() Steffen Klassert
2015-03-16 20:17 ` David Miller [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=20150316.161709.445020712639772193.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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: 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).