| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <cover.1424801573.git.joseph.salisbury@canonical.com> Date: Fri, 27 Feb 2015 15:19:19 -0500 From: Joseph Salisbury <joseph.salisbury@...onical.com> To: kamal@...onical.com Cc: alexw@...ira.com, azhou@...ira.com, pshelar@...ira.com, davem@...emloft.net, netdev@...r.kernel.org, dev@...nvswitch.org, linux-kernel@...r.kernel.org, stable@...r.kernel.org Subject: [PATCH][3.13.y-ckt][PATCH 0/1] Backport of mainline commit 4a46b24e for upstream 3.13.y-ckt. 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists