From: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, u9012063@gmail.com
Subject: [PATCH net 0/2] erspan: always reports output key to userspace
Date: Mon, 28 Jan 2019 22:23:47 +0100 [thread overview]
Message-ID: <cover.1548709944.git.lorenzo.bianconi@redhat.com> (raw)
Erspan protocol relies on output key to set session id header field.
However TUNNEL_KEY bit is cleared in order to not add key field to
the external GRE header and so the configured o_key is not reported
to userspace.
Fix the issue adding TUNNEL_KEY bit to the o_flags parameter dumping
device info
Lorenzo Bianconi (2):
net: ip_gre: always reports o_key to userspace
net: ip6_gre: always reports o_key to userspace
net/ipv4/ip_gre.c | 7 ++++++-
net/ipv6/ip6_gre.c | 7 ++++++-
2 files changed, 12 insertions(+), 2 deletions(-)
--
2.20.1
next reply other threads:[~2019-01-28 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 21:23 Lorenzo Bianconi [this message]
2019-01-28 21:23 ` [PATCH net 1/2] net: ip_gre: always reports o_key to userspace Lorenzo Bianconi
2019-01-28 21:23 ` [PATCH net 2/2] net: ip6_gre: " Lorenzo Bianconi
2019-01-30 22:00 ` [PATCH net 0/2] erspan: always reports output key " David Miller
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=cover.1548709944.git.lorenzo.bianconi@redhat.com \
--to=lorenzo.bianconi@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=u9012063@gmail.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).