From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jeff Dike <jdike@addtoit.com>
Cc: akpm@osdl.org, LKML <linux-kernel@vger.kernel.org>,
uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [PATCH 4/6] UML - free() wrapper should call libc free
Date: Wed, 02 May 2007 12:49:01 +1000 [thread overview]
Message-ID: <4637FC1D.4040300@yahoo.com.au> (raw)
In-Reply-To: <20070501182158.GA8358@c2.user-mode-linux.org>
Jeff Dike wrote:
> The libc free wrapper wasn't correctly detecting buffers obtained with
> malloc(). This is now done by seeing if the page was reserved. This is
> the case for memory which is left aside for libc and isn't given to
> the page allocator. If we free a pointer in a reserved page, it is
> given to free() rather than kfree().
I want to get rid of PG_reserved eventually. Is it possible to use PG_arch_1
for this?
>
> Signed-off-by: Jeff Dike <jdike@linux.intel.com>
> --
> arch/um/include/user.h | 1 +
> arch/um/kernel/um_arch.c | 7 +++++++
> arch/um/os-Linux/main.c | 6 +++++-
> 3 files changed, 13 insertions(+), 1 deletion(-)
>
> Index: linux-2.6.21-mm/arch/um/include/user.h
> ===================================================================
> --- linux-2.6.21-mm.orig/arch/um/include/user.h 2007-04-26 17:33:01.000000000 -0400
> +++ linux-2.6.21-mm/arch/um/include/user.h 2007-04-27 14:21:35.000000000 -0400
> @@ -27,5 +27,6 @@ extern int in_aton(char *str);
> extern int open_gdb_chan(void);
> extern size_t strlcpy(char *, const char *, size_t);
> extern size_t strlcat(char *, const char *, size_t);
> +extern int reserved_address(void *addr);
>
> #endif
> Index: linux-2.6.21-mm/arch/um/kernel/um_arch.c
> ===================================================================
> --- linux-2.6.21-mm.orig/arch/um/kernel/um_arch.c 2007-04-26 17:41:21.000000000 -0400
> +++ linux-2.6.21-mm/arch/um/kernel/um_arch.c 2007-04-27 14:30:36.000000000 -0400
> @@ -500,6 +500,13 @@ void __init check_bugs(void)
> os_check_bugs();
> }
>
> +int reserved_address(void *addr)
> +{
> + struct page *page = virt_to_page(addr);
> +
> + return(PageReserved(page));
> +}
> +
> void apply_alternatives(struct alt_instr *start, struct alt_instr *end)
> {
> }
> Index: linux-2.6.21-mm/arch/um/os-Linux/main.c
> ===================================================================
> --- linux-2.6.21-mm.orig/arch/um/os-Linux/main.c 2007-04-26 17:41:10.000000000 -0400
> +++ linux-2.6.21-mm/arch/um/os-Linux/main.c 2007-04-27 14:30:31.000000000 -0400
> @@ -266,6 +266,8 @@ void __wrap_free(void *ptr)
> /* We need to know how the allocation happened, so it can be correctly
> * freed. This is done by seeing what region of memory the pointer is
> * in -
> + * in a reserved page - free, assume the pointer was
> + * acquired with malloc, since it couldn't have been kmalloced.
> * physical memory - kmalloc/kfree
> * kernel virtual memory - vmalloc/vfree
> * anywhere else - malloc/free
> @@ -281,7 +283,9 @@ void __wrap_free(void *ptr)
> * there is a possibility for memory leaks.
> */
>
> - if((addr >= uml_physmem) && (addr < high_physmem)){
> + if(kmalloc_ok && reserved_address(ptr))
> + __real_free(ptr);
> + else if((addr >= uml_physmem) && (addr < high_physmem)){
> if(CAN_KMALLOC())
> kfree(ptr);
> }
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2007-05-02 2:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 18:21 [PATCH 4/6] UML - free() wrapper should call libc free Jeff Dike
2007-05-02 2:49 ` Nick Piggin [this message]
2007-05-02 15:41 ` Jeff Dike
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=4637FC1D.4040300@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-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