From: Steffen Klassert <steffen.klassert@secunet.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH net v3] xfrm: make local error reporting more robust
Date: Wed, 14 Aug 2013 14:22:13 +0200 [thread overview]
Message-ID: <20130814122213.GK26773@secunet.com> (raw)
In-Reply-To: <20130814110523.GG16264@order.stressinduktion.org>
On Wed, Aug 14, 2013 at 01:05:23PM +0200, Hannes Frederic Sowa wrote:
> In xfrm4 and xfrm6 we need to take care about sockets of the other
> address family. This could happen because a 6in4 or 4in6 tunnel could
> get protected by ipsec.
>
> Because we don't want to have a run-time dependency on ipv6 when only
> using ipv4 xfrm we have to embed a pointer to the correct local_error
> function in xfrm_state_afinet and look it up when returning an error
> depending on the socket address family.
>
> Thanks to vi0ss for the great bug report:
> <https://bugzilla.kernel.org/show_bug.cgi?id=58691>
>
> v2:
> a) fix two more unsafe interpretations of skb->sk as ipv6 socket
> (xfrm6_local_dontfrag and __xfrm6_output)
> v3:
> a) add an EXPORT_SYMBOL_GPL(xfrm_local_error) to fix a link error when
> building ipv6 as a module (thanks to Steffen Klassert)
>
> Reported-by: <vi0oss@gmail.com>
> Cc: Steffen Klassert <steffen.klassert@secunet.com>
> Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Applied to ipsec, thanks a lot Hannes!
prev parent reply other threads:[~2013-08-14 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 11:05 [PATCH net v3] xfrm: make local error reporting more robust Hannes Frederic Sowa
2013-08-14 12:22 ` 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=20130814122213.GK26773@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=hannes@stressinduktion.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