From: Kamal Mostafa <kamal@canonical.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: alexw@nicira.com, azhou@nicira.com, pshelar@nicira.com,
davem@davemloft.net, netdev@vger.kernel.org, dev@openvswitch.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH][3.13.y-ckt][PATCH 0/1] Backport of mainline commit 4a46b24e for upstream 3.13.y-ckt.
Date: Wed, 18 Mar 2015 16:17:57 -0700 [thread overview]
Message-ID: <1426720677.8485.90.camel@fourier> (raw)
In-Reply-To: <cover.1424801573.git.joseph.salisbury@canonical.com>
On Fri, 2015-02-27 at 15:19 -0500, Joseph Salisbury wrote:
> A large number of 'failed to flow_del' error messages are being logged
> in OpenStack deployments running the Ubuntu Trusty release with the
> 3.13 kernel. This was fixed upstream in the datapath dkms module as
> well as the 3.16 kernel.
>
> Commit 4a46b24e is the fix for this issue, and is in mainline as of
> 3.16-rc6. However, commit 4a46b24e has a dependency on commit
> 663efa36 for the define of rcu_dereference_ovsl.
>
> Commit 663efa36 is a clean cherry-pick in upstream 3.13.y-ckt.
> However, 4a46b24e required a backport. Please consider including
> mainline commit 663efa36 and the backported version of 4a46b24e in the
> next v3.13.y-ckt release.
>
> The backport for upstream stable 3.14.y is different than for
> 3.13.y-ckt and I'm not sure if this bug exists in upstream 3.14. I
> can send that backport separately if needed.
>
I have queued these for 3.13-stable:
4a46b24* openvswitch: Use exact lookup for flow_get and flow_del.
663efa3 openvswitch: Silence RCU lockdep checks from flow lookup.
*(your backport of)
Thanks Joseph,
-Kamal
prev parent reply other threads:[~2015-03-18 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 20:19 [PATCH][3.13.y-ckt][PATCH 0/1] Backport of mainline commit 4a46b24e for upstream 3.13.y-ckt Joseph Salisbury
2015-02-27 20:19 ` [PATCH][3.13.y-ckt][PATCH 1/1] openvswitch: Use exact lookup for flow_get and flow_del Joseph Salisbury
2015-02-27 20:50 ` [PATCH][3.13.y-ckt][PATCH 0/1] Backport of mainline commit 4a46b24e for upstream 3.13.y-ckt David Miller
2015-03-18 23:17 ` Kamal Mostafa [this message]
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=1426720677.8485.90.camel@fourier \
--to=kamal@canonical.com \
--cc=alexw@nicira.com \
--cc=azhou@nicira.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=joseph.salisbury@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=stable@vger.kernel.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