netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: acme@ghostprotocols.net (Arnaldo Carvalho de Melo)
To: davem@davemloft.net
Cc: marcel@holtmann.org, netdev@oss.sgi.com
Subject: [PATCH][NET] Don't call kmem_cache_create with a spinlock held
Date: Tue, 5 Apr 2005 15:25:17 -0300	[thread overview]
Message-ID: <20050405182517.GR640@conectiva.com.br> (raw)

[-- Attachment #1: Type: text/plain, Size: 117 bytes --]

Hi David,

	Please pull from:

bk://kernel.bkbits.net/acme/net-2.6

Best Regards,

                        - Arnaldo

[-- Attachment #2: proto_register_lock_fix.patch --]
[-- Type: text/plain, Size: 1173 bytes --]

===================================================================


ChangeSet@1.2245, 2005-04-05 14:52:51-03:00, acme@toy.ghostprotocols.net
  [NET] Don't call kmem_cache_create with a spinlock held
  
  This fixes the warning reported by Marcel Holtmann (Thanks!).
  
  Signed-off-by: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
  Signed-off-by: David S. Miller <davem@davemloft.net>


 sock.c |    9 ++++-----
 1 files changed, 4 insertions(+), 5 deletions(-)


diff -Nru a/net/core/sock.c b/net/core/sock.c
--- a/net/core/sock.c	2005-04-05 15:22:27 -03:00
+++ b/net/core/sock.c	2005-04-05 15:22:27 -03:00
@@ -1359,8 +1359,6 @@
 {
 	int rc = -ENOBUFS;
 
-	write_lock(&proto_list_lock);
-
 	if (alloc_slab) {
 		prot->slab = kmem_cache_create(prot->name, prot->obj_size, 0,
 					       SLAB_HWCACHE_ALIGN, NULL, NULL);
@@ -1368,14 +1366,15 @@
 		if (prot->slab == NULL) {
 			printk(KERN_CRIT "%s: Can't create sock SLAB cache!\n",
 			       prot->name);
-			goto out_unlock;
+			goto out;
 		}
 	}
 
+	write_lock(&proto_list_lock);
 	list_add(&prot->node, &proto_list);
-	rc = 0;
-out_unlock:
 	write_unlock(&proto_list_lock);
+	rc = 0;
+out:
 	return rc;
 }
 


                 reply	other threads:[~2005-04-05 18:25 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=20050405182517.GR640@conectiva.com.br \
    --to=acme@ghostprotocols.net \
    --cc=davem@davemloft.net \
    --cc=marcel@holtmann.org \
    --cc=netdev@oss.sgi.com \
    /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).