netdev - [PATCH 0/1] bridge: turn off carrier when the bridge is created

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1425971382-14177-1-git-send-email-Yanjun.Zhu@windriver.com>
Date:	Tue, 10 Mar 2015 15:09:41 +0800
From:	Zhu Yanjun <Yanjun.Zhu@...driver.com>
To:	<netdev@...r.kernel.org>, <davem@...hat.com>
Subject: [PATCH 0/1] bridge: turn off carrier when the bridge is created

V2:
   From Stephen, 
   "This is intentional. If there are no active ports in bridge, then
    we want to tell applications that packets will go nowhere."

V1:
  I made this test on ubuntu 14.04 with kernel 3,19-rc7:

  1. brctl addbr br0

  2. ifconfig br0 up

  3. ifconfig br0 (br0's status is with 'RUNNING')

  4. brctl addif br0 eth0

  5. brctl delif br0 eth0

  6. ifconfig br0 (br0's status is without 'RUNNING')

  When there is no sub-interface, the flag "RUNNING" is missing after the last sub-interface is removed.

  As such, should we keep "RUNNING" flag after the last sub-interface is removed? 

Zhu Yanjun (1):
  bridge: turn off carrier when the bridge is created

 net/bridge/br_device.c | 4 ++++
 1 file changed, 4 insertions(+)

-- 
1.9.1

--
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