netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: haiyangz@microsoft.com, haiyangz@exchange.microsoft.com
Cc: netdev@vger.kernel.org, kys@microsoft.com, olaf@aepfle.de,
	vkuznets@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next,2/2] hv_netvsc: Fix the carrier state error when data path is off
Date: Thu, 22 Jun 2017 13:30:56 -0400 (EDT)	[thread overview]
Message-ID: <20170622.133056.934912791314345535.davem@davemloft.net> (raw)
In-Reply-To: <1498088447-27282-2-git-send-email-haiyangz@exchange.microsoft.com>

From: Haiyang Zhang <haiyangz@exchange.microsoft.com>
Date: Wed, 21 Jun 2017 16:40:47 -0700

> From: Haiyang Zhang <haiyangz@microsoft.com>
> 
> When the VF NIC is opened, the synthetic NIC's carrier state is set to
> off. This tells the host to transitions data path to the VF device. But
> if startup script or user manipulates the admin state of the netvsc
> device directly for example:
>         # ifconfig eth0 down
> 	# ifconfig eth0 up
> Then the carrier state of the synthetic NIC would be on, even though the
> data path was still over the VF NIC. This patch sets the carrier state
> of synthetic NIC with consideration of the related VF state.
> 
> Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
> Reviewed-by: Stephen Hemminger <sthemmin@microsoft.com>

Applied.

  reply	other threads:[~2017-06-22 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 23:40 [PATCH net-next,1/2] hv_netvsc: Remove unnecessary var link_state from struct netvsc_device_info Haiyang Zhang
2017-06-21 23:40 ` [PATCH net-next,2/2] hv_netvsc: Fix the carrier state error when data path is off Haiyang Zhang
2017-06-22 17:30   ` David Miller [this message]
2017-06-22 17:30 ` [PATCH net-next,1/2] hv_netvsc: Remove unnecessary var link_state from struct netvsc_device_info 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=20170622.133056.934912791314345535.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=haiyangz@exchange.microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=vkuznets@redhat.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).