From: Jiri Benc <jbenc@redhat.com>
To: netdev@vger.kernel.org
Cc: pravin shelar <pshelar@ovn.org>, Eric Garver <e@erig.me>
Subject: [PATCH net-next 0/2] openvswitch: vlan fixes
Date: Tue, 4 Oct 2016 14:30:00 +0200 [thread overview]
Message-ID: <cover.1475583870.git.jbenc@redhat.com> (raw)
Fix a bug and inefficiency in the vlan handling code introduced by the
802.1AD set. Strictly speaking, both were present even before that set
but it made them more prominent.
Jiri Benc (2):
openvswitch: remove nonreachable code in vlan parsing
openvswitch: fix vlan subtraction from packet length
net/openvswitch/flow.c | 28 ++++++++--------------------
net/openvswitch/vport.c | 10 +++-------
2 files changed, 11 insertions(+), 27 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-10-04 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 12:30 Jiri Benc [this message]
2016-10-04 12:30 ` [PATCH net-next 1/2] openvswitch: remove nonreachable code in vlan parsing Jiri Benc
2016-10-05 0:06 ` Eric Garver
2016-10-05 12:53 ` Jiri Benc
2016-10-04 12:30 ` [PATCH net-next 2/2] openvswitch: fix vlan subtraction from packet length Jiri Benc
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.1475583870.git.jbenc@redhat.com \
--to=jbenc@redhat.com \
--cc=e@erig.me \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.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).