Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752755AbbBXTyT (ORCPT ); Tue, 24 Feb 2015 14:54:19 -0500 Received: from mail-gw2-out.broadcom.com ([216.31.210.63]:12541 "EHLO mail-gw2-out.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752246AbbBXTyS (ORCPT ); Tue, 24 Feb 2015 14:54:18 -0500 X-IronPort-AV: E=Sophos;i="5.09,640,1418112000"; d="scan'208";a="57908646" From: Danesh Petigara To: CC: , , , , , , , , Danesh Petigara , Subject: [PATCH] mm: cma: fix CMA aligned offset calculation Date: Tue, 24 Feb 2015 11:55:59 -0800 Message-ID: <1424807759-23311-1-git-send-email-dpetigara@broadcom.com> X-Mailer: git-send-email 1.9.1 MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1416 Lines: 45 The CMA aligned offset calculation is incorrect for non-zero order_per_bit values. For example, if cma->order_per_bit=1, cma->base_pfn= 0x2f800000 and align_order=12, the function returns a value of 0x17c00 instead of 0x400. This patch fixes the CMA aligned offset calculation. Cc: stable@vger.kernel.org Signed-off-by: Danesh Petigara Reviewed-by: Gregory Fong --- mm/cma.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/mm/cma.c b/mm/cma.c index 75016fd..58f37bd 100644 --- a/mm/cma.c +++ b/mm/cma.c @@ -70,9 +70,13 @@ static unsigned long cma_bitmap_aligned_offset(struct cma *cma, int align_order) if (align_order <= cma->order_per_bit) return 0; - alignment = 1UL << (align_order - cma->order_per_bit); - return ALIGN(cma->base_pfn, alignment) - - (cma->base_pfn >> cma->order_per_bit); + + /* + * Find a PFN aligned to the specified order and return + * an offset represented in order_per_bits. + */ + return (ALIGN(cma->base_pfn, (1UL << align_order)) + - cma->base_pfn) >> cma->order_per_bit; } static unsigned long cma_bitmap_maxno(struct cma *cma) -- 1.9.1 -- 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/