From: Greg KH <gregkh@suse.de>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: Greg KH <greg@kroah.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'devel@driverdev.osuosl.org'" <devel@driverdev.osuosl.org>,
"'virtualization@lists.osdl.org'" <virtualization@lists.osdl.org>,
Hank Janssen <hjanssen@microsoft.com>
Subject: Re: [PATCH 1/1] staging: hv: Fix missing functions for net_device_ops (resubmit)
Date: Tue, 3 Aug 2010 11:43:13 -0700 [thread overview]
Message-ID: <20100803184312.GA6150@suse.de> (raw)
In-Reply-To: <1FB5E1D5CA062146B38059374562DF728380C2F4@TK5EX14MBXC126.redmond.corp.microsoft.com>
On Tue, Aug 03, 2010 at 06:21:50PM +0000, Haiyang Zhang wrote:
> > From: Greg KH [mailto:greg@kroah.com]
> > Sent: Monday, August 02, 2010 9:30 PM
> > Why put the subject in the body of the email? This forces me to edit
> > it again :(
>
> Sure, I'll remove it.
thanks.
> > > functions. We need to put them into net_device_ops. For example,
> > > eth_change_mtu prevents setting MTU beyond 1500. This is necessary
> > > because we don't support jumbo frame at this time.
> >
> > What does this mean? Is it a bug? Just not going as fast as possible?
> > Something else?
>
> Yes, it's a bug when porting Linux IC from 2.6.27 to 2.6.32. In 2.6.27,
> the default functions for Ethernet, like eth_change_mtu(), were assigned
> by ether_setup(). But in 2.6.32, these function pointers moved to
> net_device_ops structure and no longer be assigned in ether_setup(). So we
> need to set these functions in our driver code. It will ensure the MTU won't
> be set beyong 1500. Otherwise, this can cause an error on the server side,
> because the HyperV linux driver doesn't support jumbo frame yet.
Wonderful, why not put this type of full information in the patch itself
so that people can understand and rememeber what is going on when they
look at it in a few months time?
> > > It affects kernel 2.6.32 and later, which are all versions
> > > containing Hyper-V drivers.
> >
> > So is this fixing a bug that needs to be backported to these older
> > kernels (i.e. the staging tree?) Is this something that is causing
> > people problems?
>
> Yes it should be backported. The bug can cause error on guest and host.
Than please ask for it to be backported in the future.
thanks,
greg k-h
next prev parent reply other threads:[~2010-08-03 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1FB5E1D5CA062146B38059374562DF7280E8556B@TK5EX14MBXC121.redmond.corp.microsoft.com>
2010-08-03 1:30 ` [PATCH 1/1] staging: hv: Fix missing functions for net_device_ops (resubmit) Greg KH
2010-08-03 18:21 ` Haiyang Zhang
2010-08-03 18:43 ` Greg KH [this message]
2010-08-02 17:46 Haiyang Zhang
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=20100803184312.GA6150@suse.de \
--to=gregkh@suse.de \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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).