From: Jiri Benc <jbenc@redhat.com>
To: Shmulik Ladkani <shmulik.ladkani@gmail.com>
Cc: netdev@vger.kernel.org, Simon Horman <simon.horman@netronome.com>
Subject: Re: [PATCH net-next] vxlan: set mac_header correctly in GPE mode
Date: Thu, 12 May 2016 11:07:45 +0200 [thread overview]
Message-ID: <20160512110745.6b6ab063@griffin> (raw)
In-Reply-To: <20160512094758.32bd517c@halley>
On Thu, 12 May 2016 09:47:58 +0300, Shmulik Ladkani wrote:
> Would it make sense to perform this within __iptunnel_pull_header (in
> case raw_proto is true) for all __iptunnel_pull_header callers?
raw_proto just denotes that inner_proto of ETH_P_TEB should not be
treated specially. Guessing any other special meaning based on this
flag would be unexpected and confusing. Specifically,
__iptunnel_pull_header doesn't have and should not have any notion of
the device type; although all current users of raw_proto == true are of
ARPHRD_NONE type, it's not a requirement.
> If not (meaning vxlan specific), in next few lines we have:
>
> if (!raw_proto) {
> if (!vxlan_set_mac(vxlan, vs, skb))
> goto drop;
> } else {
> skb->dev = vxlan->dev;
> skb->pkt_type = PACKET_HOST;
> }
>
> Seems more appropriate to place the missing 'skb_reset_mac_header'
> within the "else" part, which logically holds all "things to initialize
> in the skb if raw_proto is true, thus havn't called vxlan_set_mac".
I agree. I'll respin the patch.
Thanks!
Jiri
prev parent reply other threads:[~2016-05-12 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 13:55 [PATCH net-next] vxlan: set mac_header correctly in GPE mode Jiri Benc
2016-05-12 6:47 ` Shmulik Ladkani
2016-05-12 9:07 ` Jiri Benc [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=20160512110745.6b6ab063@griffin \
--to=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shmulik.ladkani@gmail.com \
--cc=simon.horman@netronome.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).