From: Anthony Wright <anthony@overnetdata.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: paul.durrant@citrix.com
Subject: Bug in hash changes to netback in 4.7.2 kernel
Date: Tue, 6 Sep 2016 13:22:39 +0100 (BST) [thread overview]
Message-ID: <17302257.22.1473164559360.JavaMail.root@zimbra.overnetdata.com> (raw)
In-Reply-To: <31342491.14.1473163834539.JavaMail.root@zimbra.overnetdata.com>
When I run Xen (4.7.0) nested in VirtualBox (5.0.24_Ubuntu r108355) with a linux-4.7.2 Dom0 kernel, none of my DomU's (linux-3.17.3) have network connectivity because they reject all packets with the error 'Invalid extra type: 4'. When I run exactly the same setup on bare metal, I don't get the error messages.
From poking around in the code this seems to be because the 4.7.2 kernel wrongly decides that the DomU's will understand EXTRA_TYPE_HASH, and so attach it to the network packet. Since the DomU's don't understand the extra info their netfront driver rejects the whole packet.
I'm guessing that the nesting is confusing the new hash code.
I also wonder if the DomU's should simply ignore extra info that they don't understand rather than rejecting the packet.
Cheers,
Anthony
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next parent reply other threads:[~2016-09-06 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <31342491.14.1473163834539.JavaMail.root@zimbra.overnetdata.com>
2016-09-06 12:22 ` Anthony Wright [this message]
2016-09-06 12:57 ` Bug in hash changes to netback in 4.7.2 kernel Paul Durrant
2016-09-06 13:37 ` Anthony Wright
2016-09-06 13:54 ` Paul Durrant
2016-11-16 5:43 Todd Fleisher
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=17302257.22.1473164559360.JavaMail.root@zimbra.overnetdata.com \
--to=anthony@overnetdata.com \
--cc=paul.durrant@citrix.com \
--cc=xen-devel@lists.xen.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.