On Monday 09 December 2013 04:56 PM, Felipe Balbi wrote: > On Mon, Dec 09, 2013 at 04:50:34PM -0500, Santosh Shilimkar wrote: >> From: Grygorii Strashko <grygorii.strashko@xxxxxx> >> >> 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 <yinghai@xxxxxxxxxx> >> Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> >> Cc: Tejun Heo <tj@xxxxxxxxxx> >> Acked-by: Tejun Heo <tj@xxxxxxxxxx> >> Signed-off-by: Grygorii Strashko <grygorii.strashko@xxxxxx> >> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@xxxxxx> > > Very minor patch but perhaps we should Cc: stable here ? not that it > matters much... > Yeah... No major fix as such from stable perspective. regards, Santosh -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>