From mboxrd@z Thu Jan 1 00:00:00 1970 From: balbi@ti.com (Felipe Balbi) Date: Mon, 9 Dec 2013 15:56:41 -0600 Subject: [PATCH v3 01/23] mm/memblock: debug: correct displaying of upper memory boundary In-Reply-To: <1386625856-12942-2-git-send-email-santosh.shilimkar@ti.com> References: <1386625856-12942-1-git-send-email-santosh.shilimkar@ti.com> <1386625856-12942-2-git-send-email-santosh.shilimkar@ti.com> Message-ID: <20131209215641.GF29143@saruman.home> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Dec 09, 2013 at 04:50:34PM -0500, Santosh Shilimkar wrote: > From: Grygorii Strashko > > When debugging is enabled (cmdline has "memblock=debug") the memblock > will display upper memory boundary per each allocated/freed memory range > wrongly. For example: > memblock_reserve: [0x0000009e7e8000-0x0000009e7ed000] _memblock_early_alloc_try_nid_nopanic+0xfc/0x12c > > The 0x0000009e7ed000 is displayed instead of 0x0000009e7ecfff > > Hence, correct this by changing formula used to calculate upper memory > boundary to (u64)base + size - 1 instead of (u64)base + size everywhere > in the debug messages. > > Cc: Yinghai Lu > Cc: Andrew Morton > Cc: Tejun Heo > Acked-by: Tejun Heo > Signed-off-by: Grygorii Strashko > Signed-off-by: Santosh Shilimkar Very minor patch but perhaps we should Cc: stable here ? not that it matters much... -- balbi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: