mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Haiyang Zhang <haiyangz@microsoft.com>
To: Sitsofe Wheeler <sitsofe@gmail.com>, KY Srinivasan <kys@microsoft.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jason Wang <jasowang@redhat.com>,
	Daniel Borkmann <dborkman@redhat.com>,
	"David S. Miller" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [hyperv] BUG at drivers/hv/channel.c:462 while changing MTU
Date: Tue, 19 Aug 2014 21:29:44 +0000	[thread overview]
Message-ID: <8dcf334714c44eeda54ecb129479719b@DFM-DB3MBX15-06.exchange.corp.microsoft.com> (raw)
In-Reply-To: <20140819123655.GC12160@sucs.org>



> -----Original Message-----
> From: Sitsofe Wheeler [mailto:sitsofe@gmail.com]
> Sent: Tuesday, August 19, 2014 8:37 AM
> To: KY Srinivasan
> Cc: Greg Kroah-Hartman; Haiyang Zhang; devel@linuxdriverproject.org;
> linux-kernel@vger.kernel.org; Jason Wang; Daniel Borkmann; David S.
> Miller; netdev@vger.kernel.org
> Subject: [hyperv] BUG at drivers/hv/channel.c:462 while changing MTU
> 
> Now we get to the issue I've been meaning to report: changing the MTU of
> a Hyper-V network interface while traffic is flowing through it triggers
> a BUG. I've seen this happen on a variety of kernels but the trace below
> is from 3.17.0-rc1.
> 
> Steps to reproduce:
> (Guests were customised Fedora 20 cloud images)
> 1.On Hyper-V VM 1 run
> iperf -s
> 2. On Hyper-V VM 2 run
> iperf -c <Hyper-V VM 1 host address> -t 200
> 3. On Hyper-V VM 2 run
> ip link set dev eth0 mtu 9000
> 
> Expected results:
> MTU of eth0 to be changed, packets to keep flowing or stop, interface to
> be at alive enough to be reconfigured.
> 
> Actual results:
> Error messages on the console, eth0 winds up dead.
> 

Thanks for the report.
I tried changing mtu while iperf is running, but unable to reproduce it.
I repeated the changing MTU test 10+ times, the link is stable, and passing 
traffic at ~8Gbps.

Could you try a Distro without customization?
I just want to narrow down the possible causes for it.

Thanks,
- Haiyang


  reply	other threads:[~2014-08-19 21:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 12:36 Sitsofe Wheeler
2014-08-19 21:29 ` Haiyang Zhang [this message]
2014-08-20  3:41   ` Sitsofe Wheeler
2014-08-25 10:48     ` Richard Weinberger
2014-08-25 14:53       ` KY Srinivasan
2014-08-25 15:07         ` Richard Weinberger
2014-08-25 17:29           ` KY Srinivasan
2014-08-25  9:36 ` Dan Carpenter
2014-08-25 17:34   ` KY Srinivasan
2014-08-25 17:50     ` Greg Kroah-Hartman
2014-08-25 18:05       ` KY Srinivasan
2014-08-25 21:43   ` Sitsofe Wheeler
2014-08-25 21:48     ` KY Srinivasan
2014-08-27  9:33       ` Sitsofe Wheeler

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=8dcf334714c44eeda54ecb129479719b@DFM-DB3MBX15-06.exchange.corp.microsoft.com \
    --to=haiyangz@microsoft.com \
    --cc=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jasowang@redhat.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sitsofe@gmail.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

all inboxes | Powered by JetHome®