Fixed a couple of fencepost errors noticed by Blaisorblade. The end of range tests should be < rather than <=. Also reworded the comment to make it less misleading. Signed-off-by: Paolo 'Blaisorblade' Giarrusso --- um-linux-2.4.27-paolo/arch/um/main.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff -puN arch/um/main.c~wrap_free arch/um/main.c --- um-linux-2.4.27/arch/um/main.c~wrap_free 2005-04-15 11:12:54.000000000 +0200 +++ um-linux-2.4.27-paolo/arch/um/main.c 2005-04-15 11:12:54.000000000 +0200 @@ -205,7 +205,7 @@ void __wrap_free(void *ptr) * kernel virtual memory - vmalloc/vfree * anywhere else - malloc/free * If kmalloc is not yet possible, then the kernel memory regions - * may not be set up yet, and the variables not initialized. So, + * may not be set up yet, and the variables not set up. So, * free is called. * * CAN_KMALLOC is checked because it would be bad to free a buffer @@ -213,11 +213,11 @@ void __wrap_free(void *ptr) * shutdown. */ - if((addr >= uml_physmem) && (addr <= high_physmem)){ + if((addr >= uml_physmem) && (addr < high_physmem)){ if(CAN_KMALLOC()) kfree(ptr); } - else if((addr >= start_vm) && (addr <= end_vm)){ + else if((addr >= start_vm) && (addr < end_vm)){ if(CAN_KMALLOC()) vfree(ptr); } _