lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 23 May 2013 14:25:19 +0900 From: HATAYAMA Daisuke <d.hatayama@...fujitsu.com> To: vgoyal@...hat.com, ebiederm@...ssion.com, akpm@...ux-foundation.org Cc: cpw@....com, kumagai-atsushi@....nes.nec.co.jp, lisa.mitchell@...com, kexec@...ts.infradead.org, linux-kernel@...r.kernel.org, zhangyanfei@...fujitsu.com, jingbai.ma@...com, linux-mm@...ck.org, riel@...hat.com, walken@...gle.com, hughd@...gle.com, kosaki.motohiro@...fujitsu.com Subject: [PATCH v8 4/9] vmalloc: make find_vm_area check in range Currently, __find_vmap_area searches for the kernel VM area starting at a given address. This patch changes this behavior so that it searches for the kernel VM area to which the address belongs. This change is needed by remap_vmalloc_range_partial to be introduced in later patch that receives any position of kernel VM area as target address. This patch changes the condition (addr > va->va_start) to the equivalent (addr >= va->va_end) by taking advantage of the fact that each kernel VM area is non-overlapping. Signed-off-by: HATAYAMA Daisuke <d.hatayama@...fujitsu.com> Acked-by: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> --- mm/vmalloc.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c index d365724..3875fa2 100644 --- a/mm/vmalloc.c +++ b/mm/vmalloc.c @@ -292,7 +292,7 @@ static struct vmap_area *__find_vmap_area(unsigned long addr) va = rb_entry(n, struct vmap_area, rb_node); if (addr < va->va_start) n = n->rb_left; - else if (addr > va->va_start) + else if (addr >= va->va_end) n = n->rb_right; else return va; -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists