From: Paul Durrant <paul.durrant@citrix.com>
To: netdev@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: Paul Durrant <paul.durrant@citrix.com>
Subject: [PATCH net-next 0/3] xen-netback: fix multiple extra info handling
Date: Thu, 10 Mar 2016 12:30:25 +0000 [thread overview]
Message-ID: <1457613028-10381-1-git-send-email-paul.durrant__40128.3852909275$1457613717$gmane$org@citrix.com> (raw)
If a frontend passes multiple extra info fragments to netback on the guest
transmit side, because xen-netback does not account for this properly, only
a single ack response will be sent. This will eventually cause processing
of the shared ring to wedge.
This series re-imports the canonical netif.h from Xen, where the ring
protocol documentation has been updated, fixes this issue in xen-netback
and also adds a patch to reduce log spam.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-03-10 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 12:30 Paul Durrant [this message]
[not found] <1457613028-10381-1-git-send-email-paul.durrant@citrix.com>
2016-03-14 2:08 ` [PATCH net-next 0/3] xen-netback: fix multiple extra info handling 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='1457613028-10381-1-git-send-email-paul.durrant__40128.3852909275$1457613717$gmane$org@citrix.com' \
--to=paul.durrant@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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).