[PATCH] Fix vq_memory_access_ok error checking
in [Kernel]
|
Prev: [git pull] PCMCIA bugfix for 2.6.34-rc3
Next: radix_tree_tag_get() is not as safe as the docs make out
From: Jeff Dike on 6 Apr 2010 16:20 Here's another small patch fixing an error path... Jeff -- Work email - jdike at linux dot intel dot com commit 7938779d9f357ede8bc3c122fd0dc9d5ec4fcf1d Author: Jeff Dike <jdike(a)addtoit.com> Date: Wed Mar 31 15:05:08 2010 -0400 vq_memory_access_ok needs to check whether mem == NULL diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index 7bd7a1e..b8e1127 100644 --- a/drivers/vhost/vhost.c +++ b/drivers/vhost/vhost.c @@ -235,6 +235,10 @@ static int vq_memory_access_ok(void __user *log_base, struct vhost_memory *mem, int log_all) { int i; + + if (!mem) + return 0; + for (i = 0; i < mem->nregions; ++i) { struct vhost_memory_region *m = mem->regions + i; unsigned long a = m->userspace_addr; -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |