netdev - [RFC VLAN 00/10]: VLAN netlink support try 2

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: <20070605143650.23717.91261.sendpatchset@localhost.localdomain>
Date:	Tue,  5 Jun 2007 16:36:51 +0200 (MEST)
From:	Patrick McHardy <kaber@...sh.net>
To:	netdev@...r.kernel.org
Cc:	Patrick McHardy <kaber@...sh.net>
Subject: [RFC VLAN 00/10]: VLAN netlink support try 2

The last VLAN patchset was outdated, sorry about the mixup. These are the
correct patches. The iproute patch I posted was correct, so no repost of
that one.


 include/linux/if_link.h  |   25 ++
 include/linux/if_vlan.h  |    7 
 net/8021q/Makefile       |    2 
 net/8021q/vlan.c         |  537 +++++++++++++++++++++++------------------------
 net/8021q/vlan.h         |   21 +
 net/8021q/vlan_dev.c     |  170 +++++---------
 net/8021q/vlan_netlink.c |  209 ++++++++++++++++++
 net/8021q/vlanproc.c     |    4 
 8 files changed, 586 insertions(+), 389 deletions(-)

Patrick McHardy (10):
      [VLAN]: Fix off-by-ones in VLAN ID checks
      [VLAN]: Convert name-based configuration functions to struct netdevice *
      [VLAN]: Move some device intialization code to dev->init callback
      [VLAN]: Move vlan_group allocation to seperate function
      [VLAN]: Split up device checks
      [VLAN]: Move device registation to seperate function
      [VLAN]: Return proper error codes in register_vlan_device
      [VLAN]: Use 32 bit value for skb->priority mapping
      [VLAN]: Keep track of number of QoS mappings
      [VLAN]: Use rtnl_link API
-
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