new

diff --git a/meta b/meta
index e8fab5de61b99be440b7fd7f2a522384271ca347..e7106ba67c49370f61d598b90d23d5414b542b36 100644 (file)
--- a/meta
+++ b/meta
@@ -1,7 +1,8 @@
 Version: 1
-Previous: eed7ab486cccb536fb6e80e955f676d0f5f3f656
-Head: 75e5b5b17d8a478b4fad5d9ee700edb943b050ba
+Previous: f58f917bd4daf38f6421176166c53cb70fd88748
+Head: 9a001f9bff4c36b828d97f9170dd6813e4860f39
 Applied:
+  kern-bug: 9a001f9bff4c36b828d97f9170dd6813e4860f39
 Unapplied:
   af-ib-conn: cf7b9e73d471477d4c7dff2592e5b0d3a7dea8ae
   addrtype: 23a84fed89ba3f6b0eb63e5f8b37c0df504d0d3e

diff --git a/patches/kern-bug b/patches/kern-bug
new file mode 100644 (file)
index 0000000..6c1c368
--- /dev/null
+++ b/patches/kern-bug
@@ -0,0 +1,28 @@
+Bottom: b6004c656a03f1cecd7bb483178086496ae46a69
+Top:    b6004c656a03f1cecd7bb483178086496ae46a69
+Author: Sean Hefty <sean.hefty@intel.com>
+Date:   2013-02-01 17:17:34 -0800
+
+librdmacm: Work-around kernel bug returning uid = 0
+
+Older kernels have a bug where it can report an event with the
+uid set to 0.  The librdmacm crashes when casting the uid to
+an rdma_cm_id and dereferencing the NULL pointer.
+
+There are a limited number of events where this can occur and
+in most cases it's safe to simply discard the event.  (This is
+what the kernel does anyway.)  However, it's possible for us
+to process an RDMA_CM_EVENT_ESTABLISHED event with the uid
+set to 0.  (See kernel commit 418edaaba96e58112b15c82b4907084e2a9caf42.)
+
+Although it's rare for this to occur, it does in fact happen
+in practice.  To work-around the kernel bug, when the uid of an
+established event is set to 0, we first try to locate the correct
+user space id based on related data before discarding the event.
+
+Signed-off-by: Sean Hefty <sean.hefty@intel.com>
+
+
+---
+
+