Messages in this thread Patch in this message | | | Date | Fri, 15 Jun 2007 11:20:31 -0400 (EDT) | From | Jason Baron <> | Subject | [PATCH] madvise_need_mmap_write() usage |
| |
hi,
i was just looking at the new madvise_need_mmap_write() call...can we avoid an extra case statement and function call as follows?
thanks,
-Jason
Signed-off-by: Jason Baron <jbaron@redhat.com>
diff --git a/mm/madvise.c b/mm/madvise.c --- a/mm/madvise.c +++ b/mm/madvise.c @@ -287,9 +287,10 @@ asmlinkage long sys_madvise(unsigned long start, size_t len_in, int behavior) struct vm_area_struct * vma, *prev; int unmapped_error = 0; int error = -EINVAL; + int write; size_t len; - if (madvise_need_mmap_write(behavior)) + if (write = madvise_need_mmap_write(behavior)) down_write(¤t->mm->mmap_sem); else down_read(¤t->mm->mmap_sem); @@ -354,7 +355,7 @@ asmlinkage long sys_madvise(unsigned long start, size_t len_in, int behavior) vma = find_vma(current->mm, start); } out: - if (madvise_need_mmap_write(behavior)) + if (write) up_write(¤t->mm->mmap_sem); else up_read(¤t->mm->mmap_sem); - 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/
| |