All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: xen-devel@lists.xensource.com
Subject: [Patch] linux: avoid kmalloc while disabling interrupts
Date: Tue, 09 Sep 2008 16:41:48 +0900	[thread overview]
Message-ID: <48C628BC.8090805@jp.fujitsu.com> (raw)

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

Hi,

We should avoid using kmalloc while interrupts is disabled.
kmalloc may sleep.

Signed-off-by: Akio Takebe <takebe_akio@jp.fujitsu.com>

Best Regards,

Akio Takebe

[-- Attachment #2: avoid_kmalloc_while_disabling_interrupts.patch --]
[-- Type: text/x-diff, Size: 1799 bytes --]

diff -r e86f9e05144a drivers/xen/pciback/controller.c
--- a/drivers/xen/pciback/controller.c	Mon Sep 08 14:02:13 2008 +0100
+++ b/drivers/xen/pciback/controller.c	Tue Sep 09 16:28:20 2008 +0900
@@ -101,15 +101,15 @@
 	unsigned long flags;
 	int ret = 0, found = 0;
 
+	/* Look to see if we already have a domain:bus for this controller */
 	spin_lock_irqsave(&dev_data->lock, flags);
-
-	/* Look to see if we already have a domain:bus for this controller */
 	list_for_each_entry(cntrl_entry, &dev_data->list, list) {
 		if (cntrl_entry->controller == dev_controller) {
 			found = 1;
 			break;
 		}
 	}
+	spin_unlock_irqrestore(&dev_data->lock, flags);
 
 	if (!found) {
 		cntrl_entry = kmalloc(sizeof(*cntrl_entry), GFP_ATOMIC);
@@ -128,9 +128,10 @@
 			dev_data->next_bus = 0;
 		}
 
+		spin_lock_irqsave(&dev_data->lock, flags);
 		INIT_LIST_HEAD(&cntrl_entry->dev_list);
-
 		list_add_tail(&cntrl_entry->list, &dev_data->list);
+		spin_unlock_irqrestore(&dev_data->lock, flags);
 	}
 
 	if (PCI_SLOT(cntrl_entry->next_devfn) > PCI_MAX_SLOTS) {
@@ -149,24 +150,24 @@
 
 	dev_entry = kmalloc(sizeof(*dev_entry), GFP_ATOMIC);
 	if (!dev_entry) {
+		spin_lock_irqsave(&dev_data->lock, flags);
 		if (list_empty(&cntrl_entry->dev_list)) {
 			list_del(&cntrl_entry->list);
 			kfree(cntrl_entry);
 		}
 		ret = -ENOMEM;
+		spin_unlock_irqrestore(&dev_data->lock, flags);
 		goto out;
 	}
 
 	dev_entry->dev = dev;
 	dev_entry->devfn = cntrl_entry->next_devfn;
 
+	spin_lock_irqsave(&dev_data->lock, flags);
 	list_add_tail(&dev_entry->list, &cntrl_entry->dev_list);
-
 	cntrl_entry->next_devfn += PCI_DEVFN(1, 0);
-
+	spin_unlock_irqrestore(&dev_data->lock, flags);
 out:
-	spin_unlock_irqrestore(&dev_data->lock, flags);
-
 	/* TODO: Publish virtual domain:bus:slot.func here. */
 
 	return ret;

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

             reply	other threads:[~2008-09-09  7:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09  7:41 Akio Takebe [this message]
2008-09-09  8:19 ` [Patch] linux: avoid kmalloc while disabling interrupts Akio Takebe
2008-09-09  8:22 ` Jan Beulich
2008-09-09  8:35   ` Akio Takebe

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=48C628BC.8090805@jp.fujitsu.com \
    --to=takebe_akio@jp.fujitsu.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.