From: Dave Chiluk <chiluk@canonical.com>
To: netdev@vger.kernel.org, davem@davemloft.net,
Wei-Chun Chao <weichunc@plumgrid.com>
Subject: Stable request for 5882a07c72093d
Date: Mon, 23 Jun 2014 10:56:55 -0500 [thread overview]
Message-ID: <1403539016-15519-1-git-send-email-chiluk@canonical.com> (raw)
Commit 5882a07c72093dc3a18e2d2b129fb200686bb6ee remedies a BUG_ON in
skb_segment. This is hit reliably in clouds that are using openvswitch for
network capabilities (which is the default network used by Openstack) on
machines that have gso offload capabilities.
This has already been reported multiple times to Canonical in numerous
openstack clouds. The fix has been integrated and tested in those clouds, and
has been show to resolve their issues.
Please include this patch for stable release.
Thank you,
Dave Chiluk
The patch follows for convenience.
next reply other threads:[~2014-06-23 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 15:56 Dave Chiluk [this message]
2014-06-23 15:56 ` [PATCH] net: fix UDP tunnel GSO of frag_list GRO packets Dave Chiluk
2014-06-23 16:18 ` Stable request for 5882a07c72093d Eric Dumazet
2014-06-23 17:35 ` Dave Chiluk
2014-06-23 22:37 ` Wei-Chun Chao
2014-06-25 23:11 ` 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=1403539016-15519-1-git-send-email-chiluk@canonical.com \
--to=chiluk@canonical.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=weichunc@plumgrid.com \
/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).