{"action":"opened","issue":{"url":"https://api.github.com/repos/ofiwg/librdmacm/issues/1","repository_url":"https://api.github.com/repos/ofiwg/librdmacm","labels_url":"https://api.github.com/repos/ofiwg/librdmacm/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/ofiwg/librdmacm/issues/1/comments","events_url":"https://api.github.com/repos/ofiwg/librdmacm/issues/1/events","html_url":"https://github.com/ofiwg/librdmacm/issues/1","id":164863263,"number":1,"title":"rshutdown hangs indefinitely","user":{"login":"toolslive","id":1249832,"avatar_url":"https://avatars.githubusercontent.com/u/1249832?v=3","gravatar_id":"","url":"https://api.github.com/users/toolslive","html_url":"https://github.com/toolslive","followers_url":"https://api.github.com/users/toolslive/followers","following_url":"https://api.github.com/users/toolslive/following{/other_user}","gists_url":"https://api.github.com/users/toolslive/gists{/gist_id}","starred_url":"https://api.github.com/users/toolslive/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/toolslive/subscriptions","organizations_url":"https://api.github.com/users/toolslive/orgs","repos_url":"https://api.github.com/users/toolslive/repos","events_url":"https://api.github.com/users/toolslive/events{/privacy}","received_events_url":"https://api.github.com/users/toolslive/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-11T15:19:03Z","updated_at":"2016-07-11T15:19:03Z","closed_at":null,"body":"If this isn't the right place to report this, then please redirect or forward.\r\n\r\nWe've seen processes that use the rsocket library hang indefinitely.\r\nHere's a backtrace from such a process (obtained via `gdb -p ...`)\r\n\r\n```\r\n#0  0x00007f7d76bdf3ad in read () at ../sysdeps/unix/syscall-template.S:81\r\n#1  0x00007f7d73e611f3 in read (__nbytes=8, __buf=0x7fff8c56c850, __fd=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44\r\n#2  __ibv_get_cq_event (channel=<optimized out>, cq=0x7fff8c56c880, cq_context=0x7fff8c56c888) at src/verbs.c:484\r\n#3  0x00007f7d75688394 in ?? () from /usr/lib/librdmacm.so.1\r\n#4  0x00007f7d75689ec0 in ?? () from /usr/lib/librdmacm.so.1\r\n#5  0x00007f7d7568d23e in rshutdown () from /usr/lib/librdmacm.so.1\r\n#6  0x00007f7d7568ec1a in rclose () from /usr/lib/librdmacm.so.1\r\n#7  0x0000000000ddf454 in ordma_rclose (fd=<optimized out>) at ordma_close.c:28\r\n```\r\n\r\nThis is version 1.0.21 (installed via debian package: librdmacm1\t1.0.21mlnx-OFED.3.3.0.0.1.33100 )\r\n\r\nIt seems to be related to this SO question:\r\nhttp://stackoverflow.com/questions/38119745/how-to-avoid-getting-stuck-in-rdma-get-recv-comp-or-ibv-get-cq-event\r\n\r\n"}}
{"actor":{"display_login":"toolslive"}}