Please sign in to comment.
memblock: memblock should be able to handle zero length operations
Commit 24aa078 ("memblock, x86: Replace memblock_x86_reserve/ free_range() with generic ones") replaced x86 specific memblock operations with the generic ones; unfortunately, it lost zero length operation handling in the process making the kernel panic if somebody tries to reserve zero length area. There isn't much to be gained by being cranky to zero length operations and panicking is almost the worst response. Drop the BUG_ON() in memblock_reserve() and update memblock_add_region/isolate_range() so that all zero length operations are handled as noops. Signed-off-by: Tejun Heo <email@example.com> Cc: firstname.lastname@example.org Reported-by: Valere Monseur <email@example.com> Bisected-by: Joseph Freeman <firstname.lastname@example.org> Tested-by: Joseph Freeman <email@example.com> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=43098 Signed-off-by: Linus Torvalds <firstname.lastname@example.org>
- Loading branch information...