Bindings hang around after bound process is killed

[GoogleCodeExporter]

After I've killed my emaild process:

 0: 721 R $.m0.net.sendemail

hangs around in /proc/kbus/bindings and I can't rebind to that symbol
despite having killed all the processes that might bind it. Killing any
process that might be stuck sending a message to it doesn't release it either.

I suspect this is another 'failing to release resources when a process dies
unexpectedly' bug.

Original issue reported on code.google.com by [email protected] on 18 Nov 2009 at 12:08

[GoogleCodeExporter]

from Donal, dated 30 Dec 2009:

I got some kbus zombies bindings just  now.  See output below from /proc/kbus/
bindings followed by output from /proc/kbus/stats

*# <device> is bound to <KSock-ID> in <process-PID> as 
<Replier|Listener> for <message-name>
  0:       33     2302  R  $.m0.net.sendemail
  0:       33     2302  L  $.m0.account.db.event.changed
  0:       33     2302  L  $.m0.db.event.*
# <device> is bound to <KSock-ID> in <process-PID> as <Replier|Listener> 
for <message-name>
# <device> is bound to <KSock-ID> in <process-PID> as <Replier|Listener> 
for <message-name>
# <device> is bound to <KSock-ID> in <process-PID> as <Replier|Listener> 
for <message-name>
# ps w | grep 2302
20772 root      2520 S    grep 2302


# more /proc/kbus/stats
dev  0: next file 663152 next msg 700790
        ksock 33 last msg 0:6107 queue 10 of 100
              read byte 0 of 0, wrote byte 0 (max 0), not sending
              outstanding requests 0 (size 16, max 1), unsent replies 0 
(max 0)
dev  1: next file 663062 next msg 17
dev  2: next file 0 next msg 0
dev  3: next file 0 next msg 0
#

Original comment by [email protected] on 4 Jan 2010 at 9:57

[GoogleCodeExporter]

From: dlafferty <[email protected]>
To: Tony Ibbs <[email protected]>
Subject: Zombie Kbus sock
Date: Wed, 27 Jan 2010 18:43:45 +0000

# <device> is bound to <KSock-ID> in <process-PID> as <Replier|Listener> 
for <message-name>
  0:     1499    13243  R  $.m0.net.sendemail
  0:     1499    13243  L  $.m0.account.db.event.changed
  0:     1499    13243  L  $.m0.db.event.*
# <device> is bound to <KSock-ID> in <process-PID> as <Replier|Listener> 
for <message-name>
# <device> is bound to <KSock-ID> in <process-PID> as <Replier|Listener> 
for <message-name>
# <device> is bound to <KSock-ID> in <process-PID> as <Replier|Listener> 
for <message-name>
# ps w | grep 13243
 4047 root      2520 S    grep 13243
#

Original comment by [email protected] on 28 Jan 2010 at 8:45

[GoogleCodeExporter]

Still there - I'm getting this regularly on ELBs.

Original comment by [email protected] on 21 Nov 2013 at 5:59