On Mon, Dec 09, 2013 at 04:50:34PM -0500, Santosh Shilimkar wrote: > From: Grygorii Strashko <[email protected]> > > 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 <[email protected]> > Cc: Andrew Morton <[email protected]> > Cc: Tejun Heo <[email protected]> > Acked-by: Tejun Heo <[email protected]> > Signed-off-by: Grygorii Strashko <[email protected]> > Signed-off-by: Santosh Shilimkar <[email protected]>
Very minor patch but perhaps we should Cc: stable here ? not that it matters much... -- balbi
signature.asc
Description: Digital signature
