From: Dean Nelson <dcn@sgi.com>
To: Steve Wise <swise@opengridcomputing.com>
Cc: jes@trained-monkey.org, avolkov@varma-el.com,
rdunlap@xenotime.net, linux-kernel@vger.kernel.org, dcn@sgi.com
Subject: Re: [PATCH 2.6.18 ] LIB Add gen_pool_destroy().
Date: Wed, 27 Sep 2006 14:51:56 -0500 [thread overview]
Message-ID: <20060927195156.GA3283@sgi.com> (raw)
In-Reply-To: <20060927153545.28235.76214.stgit@dell3.ogc.int>
Modules using the genpool allocator need to be able to destroy the data
structure when unloading.
Signed-off-by: Steve Wise <swise@opengridcomputing.com>
Signed-off-by: Dean Nelson <dcn@sgi.com>
---
Hi Steve,
I agree that the ability to destroy the allocated structures is
necessary. Thanks for doing the work. I do think it appropriate
to ensure that there are no outstanding allocations (to avoid use
after free issues) and have added that check in this new patch.
This patch has not been tested, though it does compile. I don't
have the time today. I hope you don't mind testing it? :-)
It also looks like I need to straighten out the kernel-doc
aspects of this file. I'll tackle that as a separate patch.
Thanks,
Dean
include/linux/genalloc.h | 1 +
lib/genalloc.c | 29 +++++++++++++++++++++++++++++
2 files changed, 30 insertions(+)
Index: linux-2.6/lib/genalloc.c
===================================================================
--- linux-2.6.orig/lib/genalloc.c 2006-09-27 13:42:35.000000000 -0500
+++ linux-2.6/lib/genalloc.c 2006-09-27 14:31:56.816523882 -0500
@@ -71,6 +71,35 @@
/*
+ * Destroy a memory pool.
+ *
+ * @pool: pool to destroy
+ */
+void gen_pool_destroy(struct gen_pool *pool)
+{
+ struct list_head *_chunk, *_next_chunk;
+ struct gen_pool_chunk *chunk;
+ int order = pool->min_alloc_order;
+ int bit, end_bit;
+
+
+ write_lock(&pool->lock);
+ list_for_each_safe(_chunk, _next_chunk, &pool->chunks) {
+ chunk = list_entry(_chunk, struct gen_pool_chunk, next_chunk);
+
+ end_bit = (chunk->end_addr - chunk->start_addr) >> order;
+ bit = find_next_bit(chunk->bits, end_bit, 0);
+ BUG_ON(bit < end_bit);
+
+ kfree(chunk);
+ }
+ kfree(pool);
+ return;
+}
+EXPORT_SYMBOL(gen_pool_destroy);
+
+
+/*
* Allocate the requested number of bytes from the specified pool.
* Uses a first-fit algorithm.
*
Index: linux-2.6/include/linux/genalloc.h
===================================================================
--- linux-2.6.orig/include/linux/genalloc.h 2006-09-27 13:42:34.000000000 -0500
+++ linux-2.6/include/linux/genalloc.h 2006-09-27 14:18:31.807816652 -0500
@@ -31,5 +31,6 @@
extern struct gen_pool *gen_pool_create(int, int);
extern int gen_pool_add(struct gen_pool *, unsigned long, size_t, int);
+extern void gen_pool_destroy(struct gen_pool *);
extern unsigned long gen_pool_alloc(struct gen_pool *, size_t);
extern void gen_pool_free(struct gen_pool *, unsigned long, size_t);
next prev parent reply other threads:[~2006-09-27 19:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 15:35 [PATCH 2.6.18 ] LIB Add gen_pool_destroy() Steve Wise
2006-09-27 15:51 ` Randy Dunlap
2006-09-27 15:53 ` Steve Wise
2006-09-27 15:56 ` Randy Dunlap
2006-09-27 19:59 ` Dean Nelson
2006-09-27 20:27 ` Randy Dunlap
2006-09-28 17:24 ` [PATCH] make genpool allocator adhere to kernel-doc standards Dean Nelson
2006-09-28 17:48 ` Randy Dunlap
2006-09-28 18:17 ` Dean Nelson
2006-09-27 19:51 ` Dean Nelson [this message]
2006-09-27 21:09 ` [PATCH 2.6.18 ] LIB Add gen_pool_destroy() Steve Wise
2006-09-28 13:16 ` [PATCH] add gen_pool_destroy() Dean Nelson
2006-09-28 14:51 ` Robin Holt
2006-09-28 15:48 ` Dean Nelson
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=20060927195156.GA3283@sgi.com \
--to=dcn@sgi.com \
--cc=avolkov@varma-el.com \
--cc=jes@trained-monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=swise@opengridcomputing.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