netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: razor@blackwall.org
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
	gospo@cumulusnetworks.com, kaber@trash.net,
	nikolay@cumulusnetworks.com
Subject: Re: [PATCH net] macvlan: make operstate and carrier more accurate
Date: Fri, 29 Jan 2016 12:07:27 -0800 (PST)	[thread overview]
Message-ID: <20160129.120727.2297321341636437499.davem@davemloft.net> (raw)
In-Reply-To: <1453913443-4934-1-git-send-email-razor@blackwall.org>

From: Nikolay Aleksandrov <razor@blackwall.org>
Date: Wed, 27 Jan 2016 17:50:43 +0100

> From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
> 
> Currently when a macvlan is being initialized and the lower device is
> netif_carrier_ok(), the macvlan device doesn't run through
> rfc2863_policy() and is left with UNKNOWN operstate. Fix it by adding an
> unconditional linkwatch event for the new macvlan device. Similar fix is
> already used by the 8021q device (see register_vlan_dev()). Also fix the
> inconsistent state when the lower device has been down and its carrier
> was changed (when a device is down NETDEV_CHANGE doesn't get generated).
> The second issue can be seen f.e. when we have a macvlan on top of a 8021q
> device which has been down and its real device has been changing carrier
> states, after setting the 8021q device up, the macvlan device will have
> the same carrier state as it was before even though the 8021q can now
> have a different state.
 ...
> This behaviour seems to have been present since beginning of git history.
> 
> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>

Applied, thanks Nikolay.

      reply	other threads:[~2016-01-29 20:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 16:50 [PATCH net] macvlan: make operstate and carrier more accurate Nikolay Aleksandrov
2016-01-29 20:07 ` David Miller [this message]

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=20160129.120727.2297321341636437499.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=gospo@cumulusnetworks.com \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=razor@blackwall.org \
    --cc=roopa@cumulusnetworks.com \
    /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).