[PATCH] Make sure max_memory_ranges are cleared before incremented
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On Thu, Feb 15, 2007 at 07:39:41PM +0900, Magnus Damm wrote: > Make sure max_memory_ranges are cleared before incremented > > I happened to call get_memory_ranges() twice on ia64 while debugging some > kdump issue the other day. This did not work as expected because the > variable max_memory_ranges was not cleared before being incremented. > So the second caller gets more ranges than needed. > > This is normally not a problem - get_memory_ranges() is only called once - > but I think it is good coding practice to start from a known state. > > Signed-off-by: Magnus Damm <magnus at valinux.co.jp> Thanks, applied.
[Netdev] [Linux Wireless] [Kernel Newbies] [Security] [Linux for Hams] [Netfilter] [Bugtraq] [Photo] [Yosemite] [Yosemite Forum] [MIPS Linux] [ARM Linux] [Linux RAID] [Linux Admin] [Samba] [Linux Media] [Linux Resources]