public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Iwo Mergler <iwo@call-direct.com.au>
To: linux-kernel@vger.kernel.org
Cc: Jes Sorensen <jes@trained-monkey.org>
Subject: Re: [PATCH] Fix for genalloc locking
Date: Fri, 17 Oct 2008 16:46:21 +1000	[thread overview]
Message-ID: <48F834BD.3070702@call-direct.com.au> (raw)
In-Reply-To: <48F83400.90901@call-direct.com.au>


Genalloc was using a rwlock without irqsave/irqrestore. This
caused problems when used with a mix of int/non-int calls.
Replaced all locking functions with the irqsave/restore
variants.

Signed-off-by: Iwo.Mergler@call-direct.com.au

---
 lib/genalloc.c |   21 ++++++++++++---------
 1 files changed, 12 insertions(+), 9 deletions(-)

diff --git a/lib/genalloc.c b/lib/genalloc.c
index f6d276d..337f05a 100644
--- a/lib/genalloc.c
+++ b/lib/genalloc.c
@@ -49,6 +49,7 @@ EXPORT_SYMBOL(gen_pool_create);
 int gen_pool_add(struct gen_pool *pool, unsigned long addr, size_t size,
 		 int nid)
 {
+	unsigned long rwflags;
 	struct gen_pool_chunk *chunk;
 	int nbits = size >> pool->min_alloc_order;
 	int nbytes = sizeof(struct gen_pool_chunk) +
@@ -62,9 +63,9 @@ int gen_pool_add(struct gen_pool *pool, unsigned long addr, size_t size,
 	chunk->start_addr = addr;
 	chunk->end_addr = addr + size;
 
-	write_lock(&pool->lock);
+	write_lock_irqsave(&pool->lock, rwflags);
 	list_add(&chunk->next_chunk, &pool->chunks);
-	write_unlock(&pool->lock);
+	write_unlock_irqrestore(&pool->lock, rwflags);
 
 	return 0;
 }
@@ -83,9 +84,9 @@ void gen_pool_destroy(struct gen_pool *pool)
 	struct gen_pool_chunk *chunk;
 	int order = pool->min_alloc_order;
 	int bit, end_bit;
+	unsigned long rwflags;
 
-
-	write_lock(&pool->lock);
+	write_lock_irqsave(&pool->lock, rwflags);
 	list_for_each_safe(_chunk, _next_chunk, &pool->chunks) {
 		chunk = list_entry(_chunk, struct gen_pool_chunk, next_chunk);
 		list_del(&chunk->next_chunk);
@@ -116,13 +117,14 @@ unsigned long gen_pool_alloc(struct gen_pool *pool, size_t size)
 	unsigned long addr, flags;
 	int order = pool->min_alloc_order;
 	int nbits, bit, start_bit, end_bit;
+	unsigned long rwflags;
 
 	if (size == 0)
 		return 0;
 
 	nbits = (size + (1UL << order) - 1) >> order;
 
-	read_lock(&pool->lock);
+	read_lock_irqsave(&pool->lock, rwflags);
 	list_for_each(_chunk, &pool->chunks) {
 		chunk = list_entry(_chunk, struct gen_pool_chunk, next_chunk);
 
@@ -149,12 +151,12 @@ unsigned long gen_pool_alloc(struct gen_pool *pool, size_t size)
 			while (nbits--)
 				__set_bit(start_bit++, chunk->bits);
 			spin_unlock_irqrestore(&chunk->lock, flags);
-			read_unlock(&pool->lock);
+			read_unlock_irqrestore(&pool->lock, rwflags);
 			return addr;
 		}
 		spin_unlock_irqrestore(&chunk->lock, flags);
 	}
-	read_unlock(&pool->lock);
+	read_unlock_irqrestore(&pool->lock, rwflags);
 	return 0;
 }
 EXPORT_SYMBOL(gen_pool_alloc);
@@ -174,10 +176,11 @@ void gen_pool_free(struct gen_pool *pool, unsigned long addr, size_t size)
 	unsigned long flags;
 	int order = pool->min_alloc_order;
 	int bit, nbits;
+	unsigned long rwflags;
 
 	nbits = (size + (1UL << order) - 1) >> order;
 
-	read_lock(&pool->lock);
+	read_lock_irqsave(&pool->lock, rwflags);
 	list_for_each(_chunk, &pool->chunks) {
 		chunk = list_entry(_chunk, struct gen_pool_chunk, next_chunk);
 
@@ -192,6 +195,6 @@ void gen_pool_free(struct gen_pool *pool, unsigned long addr, size_t size)
 		}
 	}
 	BUG_ON(nbits > 0);
-	read_unlock(&pool->lock);
+	read_unlock_irqrestore(&pool->lock, rwflags);
 }
 EXPORT_SYMBOL(gen_pool_free);
-- 
1.6.0



  reply	other threads:[~2008-10-17  5:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17  6:43 Fix for genalloc locking Iwo Mergler
2008-10-17  6:46 ` Iwo Mergler [this message]
2008-10-21 15:39 ` Randy Dunlap
2008-10-21 22:20   ` Iwo Mergler

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=48F834BD.3070702@call-direct.com.au \
    --to=iwo@call-direct.com.au \
    --cc=jes@trained-monkey.org \
    --cc=linux-kernel@vger.kernel.org \
    /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