On Sat, Oct 12, 2013 at 05:58:50PM -0400, 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. I kinda prefer base + size because it's easier to actually know the size but yeah, it should have been [base, base + size) and other places use base + size - 1 notation so it probably is better to stick to that. Maybe move this one to the beginning of the series? Acked-by: Tejun Heo <tj@xxxxxxxxxx> Thanks. -- tejun -- 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>