All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: jbenc@redhat.com, linville@tuxdriver.com, jesse@kernel.org,
	dsa@cumulusnetworks.com, alexei.starovoitov@gmail.com,
	netdev@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net 0/3] flowi6_tos fixes
Date: Fri, 18 Mar 2016 18:37:56 +0100	[thread overview]
Message-ID: <cover.1458320940.git.daniel@iogearbox.net> (raw)

This set is a follow-up to address Jiri's recent feedback [1] on
the flowi6_tos issue, that it is not used for IPv6 route lookups.
The three patches fix all current users of flowi6_tos and remove
the define to avoid any future confusion on this. Tested the vxlan
and geneve ones with IPv6 routing rules. For details, please see
individual patches.

[ As fixes are currently applied against net-next tree, I've rebased
  it against that. ]

Thanks!

  [1] http://patchwork.ozlabs.org/patch/592055/

Daniel Borkmann (3):
  vxlan: fix populating tclass in vxlan6_get_route
  geneve: fix populating tclass in geneve_get_v6_dst
  ipv6, trace: fix tos reporting on fib6_table_lookup

 drivers/net/geneve.c        | 11 ++++++-----
 drivers/net/vxlan.c         |  3 +--
 include/net/flow.h          |  2 +-
 include/net/ipv6.h          |  6 ++++++
 include/trace/events/fib6.h |  2 +-
 5 files changed, 15 insertions(+), 9 deletions(-)

-- 
1.9.3

             reply	other threads:[~2016-03-18 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18 17:37 Daniel Borkmann [this message]
2016-03-18 17:37 ` [PATCH net 1/3] vxlan: fix populating tclass in vxlan6_get_route Daniel Borkmann
2016-03-18 17:37 ` [PATCH net 2/3] geneve: fix populating tclass in geneve_get_v6_dst Daniel Borkmann
2016-03-18 17:37 ` [PATCH net 3/3] ipv6, trace: fix tos reporting on fib6_table_lookup Daniel Borkmann
2016-03-20 17:44 ` [PATCH net 0/3] flowi6_tos fixes 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.1458320940.git.daniel@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=alexei.starovoitov@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsa@cumulusnetworks.com \
    --cc=jbenc@redhat.com \
    --cc=jesse@kernel.org \
    --cc=linville@tuxdriver.com \
    --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 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.