From: yzhu1 <Yanjun.Zhu@windriver.com>
To: David Ahern <dsahern@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev <netdev@vger.kernel.org>,
"Wu, Kuaikuai" <Kuaikuai.Wu@windriver.com>,
"Tao, Yue" <Yue.Tao@windriver.com>
Subject: Re: If bridge have no sub-interfaces, it's status may be still with 'RUNNING'
Date: Wed, 25 Feb 2015 13:29:47 +0800 [thread overview]
Message-ID: <54ED5DCB.6020702@windriver.com> (raw)
In-Reply-To: <54ED4E47.9070304@gmail.com>
On 02/25/2015 12:23 PM, David Ahern wrote:
> On 2/24/15 7:55 PM, yzhu1 wrote:
>> Hi, Stephen && David
>>
>> Any update?
>
> As I mentioned in my last response I see no problem with the existing
> behavior -- 3.18, 3.19 and 4.0-rc1. With all of them the bridge stays
> in the running state after all interfaces are removed.
>
> David
>
>
>
Hi, David
I made tests on kernel 3.19-rc7.
1. brctl addbr br0
2. ifconfig br0 up
3. ifconfig br0 (br0's status is with 'RUNNING')
br0 Link encap:Ethernet HWaddr 0a:70:0b:06:34:8f
inet6 addr: fe80::870:bff:fe06:348f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:5054 (5.0 KB)
4. brctl addif br0 eth1
5. brctl delif br0 eth1
6. ifconfig br0 (br0's status is without 'RUNNING')
br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet6 addr: fe80::870:bff:fe06:348f/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:328 errors:0 dropped:5 overruns:0 frame:0
TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:39997 (39.9 KB) TX bytes:5760 (5.7 KB)
Please compare with the outputs of step 3 and step 6, we can find the
difference.
uname:
Linux wind-virtual-machine 3.19.0-rc7 #2 SMP Wed Jan 28 18:36:44 CST
2015 x86_64 x86_64 x86_64 GNU/Linux
So I think we should apply the latest patch to make consistent.
Any reply is appreciated.
Zhu Yanjun
next prev parent reply other threads:[~2015-02-25 5:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 9:57 If bridge have no sub-interfaces, it's status may be still with 'RUNNING' yzhu1
2015-02-13 10:00 ` yzhu1
2015-02-13 18:30 ` Stephen Hemminger
2015-02-15 7:49 ` Wu, Kuaikuai
2015-02-16 4:55 ` yzhu1
2015-02-16 15:47 ` David Ahern
2015-02-16 16:51 ` Stephen Hemminger
2015-02-17 16:14 ` Zhu, Yanjun
2015-02-25 2:55 ` yzhu1
2015-02-25 4:23 ` David Ahern
2015-02-25 5:29 ` yzhu1 [this message]
2015-02-16 16:52 ` Stephen Hemminger
2015-03-10 6:07 ` yzhu1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54ED5DCB.6020702@windriver.com \
--to=yanjun.zhu@windriver.com \
--cc=Kuaikuai.Wu@windriver.com \
--cc=Yue.Tao@windriver.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).