All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Bernat <vincent@bernat.im>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [Bridge] [PATCH net-next v1] bridge: also trigger RTM_NEWLINK when interface is released from bridge
Date: Fri, 15 Sep 2017 21:17:10 -0000	[thread overview]
Message-ID: <m3zi9vbrfp.fsf@luffy.cx> (raw)
In-Reply-To: <20170915193808.22338-1-vincent@bernat.im> (Vincent Bernat's message of "Fri, 15 Sep 2017 21:38:08 +0200")

 ❦ 15 septembre 2017 21:38 +0200, Vincent Bernat <vincent@bernat.im> :

> Currently, when an interface is released from a bridge, we get a
> RTM_DELLINK event through netlink:
>
> Deleted 2: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 master bridge0 state UNKNOWN
>     link/ether 6e:23:c2:54:3a:b3

It should be noted this only happens when using the ioctl API. When
using the netlink API, rtnetlink.c will send a RTM_NEWLINK because of
the modification.
-- 
When in doubt, tell the truth.
		-- Mark Twain

WARNING: multiple messages have this Message-ID (diff)
From: Vincent Bernat <vincent@bernat.im>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	bridge@lists.linux-foundation.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v1] bridge: also trigger RTM_NEWLINK when interface is released from bridge
Date: Fri, 15 Sep 2017 23:08:42 +0200	[thread overview]
Message-ID: <m3zi9vbrfp.fsf@luffy.cx> (raw)
In-Reply-To: <20170915193808.22338-1-vincent@bernat.im> (Vincent Bernat's message of "Fri, 15 Sep 2017 21:38:08 +0200")

 ❦ 15 septembre 2017 21:38 +0200, Vincent Bernat <vincent@bernat.im> :

> Currently, when an interface is released from a bridge, we get a
> RTM_DELLINK event through netlink:
>
> Deleted 2: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 master bridge0 state UNKNOWN
>     link/ether 6e:23:c2:54:3a:b3

It should be noted this only happens when using the ioctl API. When
using the netlink API, rtnetlink.c will send a RTM_NEWLINK because of
the modification.
-- 
When in doubt, tell the truth.
		-- Mark Twain

  reply	other threads:[~2017-09-15 21:17 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-15 19:38 [PATCH net-next v1] bridge: also trigger RTM_NEWLINK when interface is released from bridge Vincent Bernat
2017-09-15 19:47 ` [Bridge] " Vincent Bernat
2017-09-15 21:08 ` Vincent Bernat [this message]
2017-09-15 21:17   ` Vincent Bernat
2017-09-16 14:18   ` [PATCH net-next v2] " Vincent Bernat
2017-09-16 14:18     ` [Bridge] " Vincent Bernat
2017-09-20 21:09     ` David Miller
2017-09-20 21:09       ` David Miller
2017-09-20 21:57       ` [Bridge] " David Ahern
2017-09-20 21:57         ` David Ahern
2017-09-20 22:12         ` Vincent Bernat
2017-09-20 22:13           ` [Bridge] " Vincent Bernat
2017-09-20 22:41           ` David Miller
2017-09-20 22:41             ` David Miller
2017-09-20 23:21         ` [Bridge] " Stephen Hemminger
2017-09-20 23:21           ` Stephen Hemminger
2017-09-21 10:04           ` Vincent Bernat
2017-09-21 10:04             ` [Bridge] " Vincent Bernat
2017-09-21 15:09             ` Roopa Prabhu
2017-09-21 15:09               ` Roopa Prabhu
2017-09-21 15:31               ` Vincent Bernat
2017-09-21 15:31                 ` [Bridge] " Vincent Bernat
2017-09-21 10:05           ` [net-next v3] bridge: trigger RTM_NEWLINK when interface is modified by bridge ioctl Vincent Bernat
2017-09-21 10:05             ` [Bridge] " Vincent Bernat
2017-09-21 15:15             ` Stephen Hemminger
2017-09-21 15:15               ` Stephen Hemminger
2017-09-21 15:45               ` Vincent Bernat
2017-09-21 15:45                 ` [Bridge] " Vincent Bernat
2017-09-21 16:43             ` David Ahern
2017-09-21 16:43               ` David Ahern
2017-09-21 17:20               ` [Bridge] " Roopa Prabhu
2017-09-21 17:20                 ` Roopa Prabhu
2017-09-21 17:29                 ` [Bridge] " David Ahern
2017-09-21 17:29                   ` David Ahern
2017-09-21 22:45             ` [Bridge] " David Miller
2017-09-21 22:45               ` David Miller

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=m3zi9vbrfp.fsf@luffy.cx \
    --to=vincent@bernat.im \
    --cc=bridge@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.