netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v2 0/3] virtio-net: backport error handling bugfix
Date: Thu, 26 Dec 2013 15:32:44 +0200	[thread overview]
Message-ID: <1388064752-15734-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 change split out for ease of
review - that's why 2/2 is here even though it's not
stricktly a bugfix - the code becomes too confusing without it.

Please review and consider for stable.

Changes from v1:
	- include patch 3/3 as suggested by Michael
	- tweak commit log as suggested by Jason

Michael S. Tsirkin (3):
  virtio_net: fix error handling for mergeable buffers
  virtio-net: make all RX paths handle errors consistently
  virtio_net: don't leak memory or block when too many frags

 drivers/net/virtio_net.c | 103 +++++++++++++++++++++++++++++++++--------------
 1 file changed, 73 insertions(+), 30 deletions(-)

-- 
MST

             reply	other threads:[~2013-12-26 13:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-26 13:32 Michael S. Tsirkin [this message]
2013-12-26 13:32 ` [PATCH stable v2 1/3] virtio_net: fix error handling for mergeable buffers Michael S. Tsirkin
2013-12-27  3:19   ` Jason Wang
2013-12-26 13:32 ` [PATCH stable v2 2/3] virtio-net: make all RX paths handle errors consistently Michael S. Tsirkin
2013-12-27  3:19   ` Jason Wang
2013-12-26 13:32 ` [PATCH stable v2 3/3] virtio_net: don't leak memory or block when too many frags Michael S. Tsirkin
2014-01-02  4:16 ` [PATCH stable v2 0/3] virtio-net: backport error handling bugfix 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=1388064752-15734-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).