From: Stephen Hemminger <stephen@networkplumber.org>
To: "I-Dawson, Peter A" <Peter.A.Dawson@boeing.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] ip6_tunnel, ip6_gre: fix setting of DSCP on encapsulated packets
Date: Wed, 17 May 2017 18:18:00 -0700 [thread overview]
Message-ID: <20170517181800.07788dd8@xeon-e3> (raw)
In-Reply-To: <5fba416f3f644db2b1f51e54724ef6ba@XCH15-07-02.nw.nos.boeing.com>
On Thu, 18 May 2017 01:11:01 +0000
"I-Dawson, Peter A" <Peter.A.Dawson@boeing.com> wrote:
> This fix addresses two problems in the way the DSCP field is formulated on the
> encapsulating header of IPv6 tunnels.
> This fix addresses Bug 195661. https://bugzilla.kernel.org/show_bug.cgi?id=195661
>
> 1) The IPv6 tunneling code was manipulating the DSCP field of the encapsulating
> packet using the 32b flowlabel. Since the flowlabel is only the lower 20b it
> was incorrect to assume that the upper 12b containing the DSCP and ECN fields
> would remain intact when formulating the encapsulating header. This fix
> handles the 'inherit' and 'fixed-value' DSCP cases explicitly using the extant
> dsfield u8 variable.
>
> 2) The use of INET_ECN_encapsulate(0, dsfield) in ip6_tnl_xmit was incorrect
> and resulted in the DSCP value always being set to 0.
> ---
> net/ipv6/ip6_gre.c | 18 ++++++++++--------
> net/ipv6/ip6_tunnel.c | 28 +++++++++++++++++-----------
> 2 files changed, 27 insertions(+), 19 deletions(-)
This patch looks correct, but has trivial style issues like using spaces
instead of tabs and other junk. Please run checkpatch.pl, look at the
results and resubmit.
next prev parent reply other threads:[~2017-05-18 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 1:11 [PATCH] ip6_tunnel, ip6_gre: fix setting of DSCP on encapsulated packets I-Dawson, Peter A
2017-05-18 1:18 ` Stephen Hemminger [this message]
[not found] ` <579256095bc540bab2668f55a6a2c25b@XCH15-07-02.nw.nos.boeing.com>
2017-05-18 2:49 ` Peter Dawson
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=20170517181800.07788dd8@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=Peter.A.Dawson@boeing.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 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).