Bonding simplifications and netns support
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 19 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | net: Allow devices to specify a device specific sysfs group.include/ net/ | +6 | 0 replies | |
| 2/6 | bond: Simply bond sysfs group creationdrivers/ drivers/ drivers/ | +4 | 0 replies | |
| 3/6 | bond: Simplify bond_create.drivers/ | +4 | 0 replies | |
| 4/6 | bond: Simplify bond device destructiondrivers/ | +16 | 0 replies | |
| 5/6 | bond: Implement a basic set of rtnl link opsdrivers/ | +30 | 7 replies | |
| 6/6 | bond: Add support for multiple network namespacesdrivers/ drivers/ drivers/ +3 more | +99 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] Bonding simplifications and netns support
I recently had it pointed out to me that the bonding driver does not work in a network namespace. So I have simplified the bonding driver a bit, added support for ip link add and ip link del, and finally made the bonding driver work in multiple network namespaces.
The most note worthy change in the patchset is the addition of support in the networking core for registering a sysfs group for a device.
Using this in the bonding driver simplifies the code and removes a userspace race between actions triggered by the netlink event and the bonding sysfs attributes appearing.
Eric