Subject: [merged] mm-zbud-fix-condition-check-on-allocation-size.patch removed from -mm tree To: heesub.shin@xxxxxxxxxxx,bob.liu@xxxxxxxxxx,d.j.shin@xxxxxxxxxxx,sjenning@xxxxxxxxxxxxxxxxxx,sunae.seo@xxxxxxxxxxx,mm-commits@xxxxxxxxxxxxxxx From: akpm@xxxxxxxxxxxxxxxxxxxx Date: Mon, 05 Aug 2013 12:05:55 -0700 The patch titled Subject: mm: zbud: fix condition check on allocation size has been removed from the -mm tree. Its filename was mm-zbud-fix-condition-check-on-allocation-size.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Heesub Shin <heesub.shin@xxxxxxxxxxx> Subject: mm: zbud: fix condition check on allocation size zbud_alloc() incorrectly verifies the size of allocation limit. It should deny the allocation request greater than (PAGE_SIZE - ZHDR_SIZE_ALIGNED - CHUNK_SIZE), not (PAGE_SIZE - ZHDR_SIZE_ALIGNED) which has no remaining spaces for its buddy. There is no point in spending the entire zbud page storing only a single page, since we don't have any benefits. Signed-off-by: Heesub Shin <heesub.shin@xxxxxxxxxxx> Acked-by: Seth Jennings <sjenning@xxxxxxxxxxxxxxxxxx> Cc: Bob Liu <bob.liu@xxxxxxxxxx> Cc: Dongjun Shin <d.j.shin@xxxxxxxxxxx> Cc: Sunae Seo <sunae.seo@xxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/zbud.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN mm/zbud.c~mm-zbud-fix-condition-check-on-allocation-size mm/zbud.c --- a/mm/zbud.c~mm-zbud-fix-condition-check-on-allocation-size +++ a/mm/zbud.c @@ -257,7 +257,7 @@ int zbud_alloc(struct zbud_pool *pool, i if (size <= 0 || gfp & __GFP_HIGHMEM) return -EINVAL; - if (size > PAGE_SIZE - ZHDR_SIZE_ALIGNED) + if (size > PAGE_SIZE - ZHDR_SIZE_ALIGNED - CHUNK_SIZE) return -ENOSPC; chunks = size_to_chunks(size); spin_lock(&pool->lock); _ Patches currently in -mm which might be from heesub.shin@xxxxxxxxxxx are -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html