linux-kernel - [PATCH net-next 0/2] bonding: use correct ether type for alb

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 13 Mar 2014 12:41:56 +0100
From:	Veaceslav Falico <vfalico@...hat.com>
To:	netdev@...r.kernel.org
Cc:	Jay Vosburgh <fubar@...ibm.com>,
	Andy Gospodarek <andy@...yhouse.net>,
	"David S. Miller" <davem@...emloft.net>,
	Stefan Richter <stefanr@...6.in-berlin.de>,
	Simon Wunderlich <sw@...onwunderlich.de>,
	Neil Jerram <Neil.Jerram@...aswitch.com>,
	Simon Horman <horms@...ge.net.au>,
	Arvid Brodin <Arvid.Brodin@...n.com>,
	linux-kernel@...r.kernel.org, Veaceslav Falico <vfalico@...hat.com>
Subject: [PATCH net-next 0/2] bonding: use correct ether type for alb

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@...ibm.com>
CC: Andy Gospodarek <andy@...yhouse.net>
CC: "David S. Miller" <davem@...emloft.net>
CC: Stefan Richter <stefanr@...6.in-berlin.de>
CC: Simon Wunderlich <sw@...onwunderlich.de>
CC: Neil Jerram <Neil.Jerram@...aswitch.com>
CC: Simon Horman <horms@...ge.net.au>
CC: Arvid Brodin <Arvid.Brodin@...n.com>
CC: netdev@...r.kernel.org
CC: linux-kernel@...r.kernel.org
Signed-off-by: Veaceslav Falico <vfalico@...hat.com>

---
 drivers/net/bonding/bond_alb.c | 2 +-
 include/uapi/linux/if_ether.h  | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/