From: INAKOSHI Hiroya <inakoshi.hiroya@jp.fujitsu.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH] incorrect xfree for mini-os
Date: Wed, 02 Apr 2008 19:43:29 +0900 [thread overview]
Message-ID: <47F36351.4040106@jp.fujitsu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 292 bytes --]
xfree in extras/mini-os/lib/xmalloc.c is incorrect.
It has to check first if the memory to free is so big as to be freed
directly by free_pages.
mini-os domains crash without this patch if they don't configure vfb
correctly.
Signed-off-by: INAKOSHI Hiroya <inakoshi.hiroya@jp.fujitsu.com>
[-- Attachment #2: minios-incorrect-xfree.patch --]
[-- Type: text/plain, Size: 942 bytes --]
diff -r db943e8d1051 extras/mini-os/lib/xmalloc.c
--- a/extras/mini-os/lib/xmalloc.c Tue Apr 01 10:09:33 2008 +0100
+++ b/extras/mini-os/lib/xmalloc.c Wed Apr 02 19:34:40 2008 +0900
@@ -208,6 +208,13 @@ void xfree(const void *p)
pad = (struct xmalloc_pad *)p - 1;
hdr = (struct xmalloc_hdr *)((char *)p - pad->hdr_size);
+ /* Big allocs free directly. */
+ if ( hdr->size >= PAGE_SIZE )
+ {
+ free_pages(hdr, get_order(hdr->size));
+ return;
+ }
+
/* We know hdr will be on same page. */
if(((long)p & PAGE_MASK) != ((long)hdr & PAGE_MASK))
{
@@ -220,13 +227,6 @@ void xfree(const void *p)
{
printk("Should not be previously freed\n");
*(int*)0=0;
- }
-
- /* Big allocs free directly. */
- if ( hdr->size >= PAGE_SIZE )
- {
- free_pages(hdr, get_order(hdr->size));
- return;
}
/* Merge with other free block, or put in list. */
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2008-04-02 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 10:43 INAKOSHI Hiroya [this message]
2008-04-02 10:52 ` [PATCH] incorrect xfree for mini-os Samuel Thibault
2008-04-02 14:45 ` Keir Fraser
2008-04-02 21:40 ` Samuel Thibault
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=47F36351.4040106@jp.fujitsu.com \
--to=inakoshi.hiroya@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.