linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladislav Bolkhovitin <vst@vlnb.net>
To: linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, scst-devel@lists.sourceforge.net
Subject: [PATCH][iSCSI-SCST]: Clean up netlink socket correctly
Date: Fri, 30 Jan 2009 21:20:32 +0300	[thread overview]
Message-ID: <498344F0.3010109@vlnb.net> (raw)

2.6.25 introduced netlink_socket_release(), to be used to clean up netlink sockets
correctly taking care of namespaces. Fix now wrong sock_release() call in iSCSI-SCST.

Signed-off-by: Arne Redlich <agr@powerkom-dd.de>
Signed-off-by: Vladislav Bolkhovitin <vst@vlnb.net>

 event.c |    3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

Index: iscsi-scst/kernel/event.c
===================================================================
--- iscsi-scst/kernel/event.c	(revision 648)
+++ iscsi-scst/kernel/event.c	(working copy)
@@ -142,6 +142,10 @@ int __init event_init(void)
 
 void event_exit(void)
 {
- 	if (nl)
- 		sock_release(nl->sk_socket);
+	netlink_kernel_release(nl);
 }


                 reply	other threads:[~2009-01-30 18:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=498344F0.3010109@vlnb.net \
    --to=vst@vlnb.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=scst-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).