From: Veaceslav Falico <vfalico@redhat.com>
To: netdev@vger.kernel.org
Cc: Jay Vosburgh <fubar@us.ibm.com>,
Andy Gospodarek <andy@greyhouse.net>,
"David S. Miller" <davem@davemloft.net>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Simon Wunderlich <sw@simonwunderlich.de>,
Neil Jerram <Neil.Jerram@metaswitch.com>,
Simon Horman <horms@verge.net.au>,
Arvid Brodin <Arvid.Brodin@xdin.com>,
linux-kernel@vger.kernel.org,
Veaceslav Falico <vfalico@redhat.com>
Subject: [PATCH net-next 0/2] bonding: use correct ether type for alb
Date: Thu, 13 Mar 2014 12:41:56 +0100 [thread overview]
Message-ID: <1394710918-29540-1-git-send-email-vfalico@redhat.com> (raw)
Hi,
There have been reports that, while using the ETH_P_LOOP ether type
(0x0060), the ether type is treated as its packet length.
To avoid that and to not break already existing apps - add new ether type
ETH_P_LOOPBACK that contains the correct id - 0x9000.
CC: Jay Vosburgh <fubar@us.ibm.com>
CC: Andy Gospodarek <andy@greyhouse.net>
CC: "David S. Miller" <davem@davemloft.net>
CC: Stefan Richter <stefanr@s5r6.in-berlin.de>
CC: Simon Wunderlich <sw@simonwunderlich.de>
CC: Neil Jerram <Neil.Jerram@metaswitch.com>
CC: Simon Horman <horms@verge.net.au>
CC: Arvid Brodin <Arvid.Brodin@xdin.com>
CC: netdev@vger.kernel.org
CC: linux-kernel@vger.kernel.org
Signed-off-by: Veaceslav Falico <vfalico@redhat.com>
---
drivers/net/bonding/bond_alb.c | 2 +-
include/uapi/linux/if_ether.h | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
next reply other threads:[~2014-03-13 11:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 11:41 Veaceslav Falico [this message]
2014-03-13 11:41 ` [PATCH net-next 1/2] ether: add loopback type ETH_P_LOOPBACK Veaceslav Falico
2014-03-13 11:41 ` [PATCH net-next 2/2] bonding: use the correct ether type for alb Veaceslav Falico
2014-03-14 18:29 ` David Miller
2014-03-14 18:42 ` Veaceslav Falico
2014-03-14 19:12 ` David Miller
2014-03-14 19:27 ` Jay Vosburgh
2014-03-14 19:47 ` Veaceslav Falico
2014-03-15 2:21 ` [PATCH net-next 0/2] bonding: use " 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=1394710918-29540-1-git-send-email-vfalico@redhat.com \
--to=vfalico@redhat.com \
--cc=Arvid.Brodin@xdin.com \
--cc=Neil.Jerram@metaswitch.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=sw@simonwunderlich.de \
/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).