From: "Michael S. Tsirkin" <mst@redhat.com>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: [PATCH stable 0/2] virtio-net: backport error handling bugfix
Date: Wed, 25 Dec 2013 16:56:18 +0200 [thread overview]
Message-ID: <1387983339-1172-1-git-send-email-mst@redhat.com> (raw)
Error handling for virtio-net mergeable buffers was broken
for a long time. Backport recent bugfix to a stable
kernel.
Please note that it's really a single patch split out in two for ease of
review: if we apply 1/2 only the code is correct but ugly and confusing, so I
think it's best to backport both patches 1/2 and 2/2 same as upstream has them.
Please review and consider for stable.
Michael S. Tsirkin (2):
virtio_net: fix error handling for mergeable buffers
virtio-net: make all RX paths handle erors consistently
drivers/net/virtio_net.c | 103 ++++++++++++++++++++++++++++++++++-------------
1 file changed, 74 insertions(+), 29 deletions(-)
--
MST
next reply other threads:[~2013-12-25 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-25 14:56 Michael S. Tsirkin [this message]
2013-12-25 14:56 ` [PATCH stable 1/2] virtio_net: fix error handling for mergeable buffers Michael S. Tsirkin
2013-12-25 18:33 ` Michael Dalton
2013-12-25 19:19 ` Michael S. Tsirkin
2013-12-26 6:35 ` Michael Dalton
2013-12-26 7:28 ` Jason Wang
2013-12-25 14:56 ` [PATCH stable 2/2] virtio-net: make all RX paths handle erors consistently Michael S. Tsirkin
2013-12-26 7:28 ` Jason Wang
2013-12-26 7:31 ` Zhi Yong Wu
2013-12-25 20:13 ` [PATCH stable] virtio_net: don't leak memory or block when too many frags Michael S. Tsirkin
2013-12-26 6:35 ` Michael Dalton
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=1387983339-1172-1-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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).