All of lore.kernel.org
 help / color / mirror / Atom feed
From: glommer@br.ibm.com (Glauber de Oliveira Costa)
To: xen-devel@lists.xensource.com
Subject: [PATCH] Null pointer dereference at free_vm_area()
Date: Mon, 26 Dec 2005 13:58:57 -0200	[thread overview]
Message-ID: <20051226155857.GA14912@br.ibm.com> (raw)

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

Hi folks,

The free_vm_area() function may crash if it gets a NULL pointer as a
parameter. I do think that the right behaviour should be returning in
this case. This is, for example, the same behaviour of kfree(), and as
alloc_vm_area() may also return NULL, it may lead to a more elegant 
alloc/free sequence in case of a fail.

In case you agree with that, a patch follows.

Signed-off-by: Glauber de Oliveira Costa <glommer@br.ibm.com>

-- 
glommer

[-- Attachment #2: free_return_null --]
[-- Type: text/plain, Size: 390 bytes --]

diff -r 829517be689f linux-2.6-xen-sparse/drivers/xen/util.c
--- a/linux-2.6-xen-sparse/drivers/xen/util.c	Fri Dec 23 15:42:46 2005
+++ b/linux-2.6-xen-sparse/drivers/xen/util.c	Mon Dec 26 15:47:50 2005
@@ -35,6 +35,8 @@
 void free_vm_area(struct vm_struct *area)
 {
 	struct vm_struct *ret;
+	if (!area)
+		return;
 	ret = remove_vm_area(area->addr);
 	BUG_ON(ret != area);
 	kfree(area);

[-- 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:[~2005-12-26 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26 15:58 Glauber de Oliveira Costa [this message]
2005-12-27 15:54 ` [PATCH] Null pointer dereference at free_vm_area() Vincent Hanquez
2005-12-27 16:17   ` Glauber de Oliveira Costa

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=20051226155857.GA14912@br.ibm.com \
    --to=glommer@br.ibm.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.