From: Steffen Klassert <steffen.klassert@secunet.com>
To: Alexander Duyck <alexander.h.duyck@redhat.com>
Cc: <netdev@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
<davem@davemloft.net>, <herbert@gondor.apana.org.au>
Subject: Re: [ipsec PATCH 0/3] Preserve skb->mark through VTI tunnels
Date: Thu, 28 May 2015 07:58:48 +0200 [thread overview]
Message-ID: <20150528055845.GH27342@secunet.com> (raw)
In-Reply-To: <20150527141042.1576.47399.stgit@ahduyck-vm-fedora22>
On Wed, May 27, 2015 at 07:16:37AM -0700, Alexander Duyck wrote:
> These patches are meant to try and address the fact the VTI tunnels are
> currently overwriting the skb->mark value. I am generally happy with the
> first two patches, however the third patch still modifies the skb->mark,
> though it undoes after the fact.
>
> The main problem I am trying to address is the fact that currently if I use
> an v6 over v6 VTI tunnel I cannot receive any traffic on the interface as
> the skb->mark is bleeding through and causing the traffic to be dropped.
>
> ---
>
> Alexander Duyck (3):
> ip_vti/ip6_vti: Do not touch skb->mark on xmit
> xfrm: Override skb->mark with tunnel->parm.i_key in xfrm_input
> ip_vti/ip6_vti: Preserve skb->mark after rcv_cb call
All applied to the ipsec tree, thanks a lot Alexander!
prev parent reply other threads:[~2015-05-28 5:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 14:16 [ipsec PATCH 0/3] Preserve skb->mark through VTI tunnels Alexander Duyck
2015-05-27 14:16 ` [ipsec PATCH 1/3] ip_vti/ip6_vti: Do not touch skb->mark on xmit Alexander Duyck
2015-05-27 14:16 ` [ipsec PATCH 2/3] xfrm: Override skb->mark with tunnel->parm.i_key in xfrm_input Alexander Duyck
2015-05-27 14:16 ` [ipsec PATCH 3/3] ip_vti/ip6_vti: Preserve skb->mark after rcv_cb call Alexander Duyck
2015-05-28 5:58 ` 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=20150528055845.GH27342@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=alexander.h.duyck@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).