FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 07-03-2012, 04:55 PM
Jonathan Nieder
 
Default Bug#680094: iproute: ip link can't remove bridge created with brctl

reassign 680094 src:linux 3.3.4-1~experimental.1
tags 680094 + upstream patch
quit

Hi,

Andreas Henriksson wrote:

> Fixed upstream in the commit Stephen Hemminger pointed out (read bug
> backlog).

Thanks. For reference:

commit 149ddd83a92b
Author: stephen hemminger <shemminger@vyatta.com>
Date: Tue Jun 26 05:48:45 2012 +0000

bridge: Assign rtnl_link_ops to bridge devices created via ioctl (v2)

This ensures that bridges created with brctl(8) or ioctl(2) directly
also carry IFLA_LINKINFO when dumped over netlink. This also allows
to create a bridge with ioctl(2) and delete it with RTM_DELLINK.

Signed-off-by: Thomas Graf <tgraf@suug.ch>
Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

This is in the netdev stable queue[1] so it should be part of upstream
stable kernels soonish.

Can you say a little more about the background? Is this a regression?
What kernel versions are affected? Is this going to create trouble
during squeeze → wheezy upgrades for people upgrading userspace before
the kernel or vice versa?

Hope that helps,
Jonathan

[1] http://patchwork.ozlabs.org/bundle/davem/stable/?state=*



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120703165544.GA11147@burratino
 
Old 07-03-2012, 05:40 PM
Andreas Henriksson
 
Default Bug#680094: iproute: ip link can't remove bridge created with brctl

On Tue, Jul 03, 2012 at 11:55:44AM -0500, Jonathan Nieder wrote:
[...]
> Can you say a little more about the background? Is this a regression?

I don't know if I can, but I'll try....

The main background is that the ioctl interfaces traditionally used
by tools like ifconfig, route, ... (net-tools), bridge-utils, etc
was considered not appropriate and the new "netlink" (socket) interface
was invented which gives alot more power oven the traditional interface.

The iproute2 suite was created to have a basic administrative userspace
application to use the new netlink interface.

Some functionality is still quite new on the netlink side (both in
iproute2 and linux). Among these are the bridging commands.

Adding bridges via iproute2 seems to have been introduced in 2011
(commit bb900b27a2f49b37bc38c08e656ea13048fee13b).

This is thus not a real regression, but one hurdle in switching over
from old ioctl based tools to new netlink based tools.

> What kernel versions are affected? Is this going to create trouble

All versions are affected (I guess sarge kernel doesn't support
much bridge functionality over netlink at all), while current wheezy
kernel only has a problem with removing brctl created bridges.

> during squeeze → wheezy upgrades for people upgrading userspace before
> the kernel or vice versa?

I don't think ifupdown has any bridge functionality, so I don't see a
direct connection in the dist-upgrade case. Indirectly, one would
hope that people might do an overhaul of their system in connection
to dist-upgrades and then it could affect people....

This is mainly just a runtime annoyance, when you do a switch over
from bridge-utils (brctl) to iproute2 (ip) for managing your bridges.

It's not a large problem, since if you really want to switch you can
just get rid of your old bridges by rebooting (and while at it testing your
scripts to work correctly during system bootup!)....
ie. if you create your bridges with iproute2, you won't have a problem.

--
Andreas Henriksson



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120703174033.GA27174@amd64.fatal.se">http://lists.debian.org/20120703174033.GA27174@amd64.fatal.se
 
Old 07-03-2012, 05:44 PM
Andreas Henriksson
 
Default Bug#680094: iproute: ip link can't remove bridge created with brctl

FWIW, a last note....
Running "git log net/bridge/br_netlink.c" in a kernel tree should give
you both a quite good history lesson on the introduction of managing
bridges via netlink (iproute2) and the future upcoming features which
you'll be missing out on if you stay with the ioctl based bridge-utils.

--
Andreas Henriksson



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120703174446.GA27337@amd64.fatal.se">http://lists.debian.org/20120703174446.GA27337@amd64.fatal.se
 
Old 07-03-2012, 06:15 PM
Jonathan Nieder
 
Default Bug#680094: iproute: ip link can't remove bridge created with brctl

found 680094 linux-2.6/2.6.32-45
found 680094 linux/3.2.21-3
quit

Andreas Henriksson wrote:

> This is thus not a real regression, but one hurdle in switching over
> from old ioctl based tools to new netlink based tools.

Thanks for a clear and sensible explanation. (I should have just read
the original report to save time.) Marking squeeze and wheezy kernels
as affected.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120703181546.GA16063@burratino
 

Thread Tools




All times are GMT. The time now is 10:23 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org