netdev - [PATCH net-next (TAKE 4) 0/6] IPv6 over Firewire

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]

Message-ID: <51509696.6060600@linux-ipv6.org>
Date:	Tue, 26 Mar 2013 03:25:26 +0900
From:	YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>
To:	davem@...emloft.net, stefanr@...6.in-berlin.de
CC:	netdev@...r.kernel.org, linux1394-devel@...ts.sourceforge.net,
	stephan.gatzka@...il.com, yoshfuji@...ux-ipv6.org
Subject: [PATCH net-next (TAKE 4) 0/6] IPv6 over Firewire

This is take 4 of supporting IPv6 over Firewire (IEEE 1394) based on
RFC3146.

Take 3->4:
- Fix receiving 1394 ARP, which comes without arp$tha.
- Remove rfc3146 unit directory on module exit.
- other minor clean-ups - minimize diffs.

YOSHIFUJI Hideaki (6):
  firewire net: Accept IPv4 and ARP only.
  firewire net: Send L2 multicast via GASP.
  firewire net: Allocate address handler before registering net_device.
  firewire net: Ignore spd and max_payload advertised by ARP.
  firewire net, ipv4 arp: Extend hardware address and remove
    driver-level packet inspection.
  firewire net, ipv6: IPv6 over Firewire (RFC3146) support.

 drivers/firewire/Kconfig |    6 +-
 drivers/firewire/net.c   |  301 +++++++++++++++++++++-------------------------
 include/linux/if_arp.h   |   12 +-
 include/net/firewire.h   |   25 ++++
 net/ipv4/arp.c           |   27 ++++-
 net/ipv6/addrconf.c      |   20 ++-
 6 files changed, 213 insertions(+), 178 deletions(-)
 create mode 100644 include/net/firewire.h

-- 
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html