[PATCH 1/7] initialize pfn_memhole in get_num_dumpable_cyclic
Vivek Goyal
vgoyal at redhat.com
Fri Jul 11 07:19:19 PDT 2014
Hi Bao,
There is no patch 0 describing what this patch series is all about and
what it is fixing?
Thanks
Vivek
On Fri, Jul 11, 2014 at 03:15:58PM +0800, Baoquan He wrote:
> This is a code bug. In initialize_2nd_bitmap_cyclic pfn_memhole is
> calculated, however it's not initialized before that. If an available
> pfn_memhole is wanted after get_num_dumpable_cyclic invocation,
> initializing pfn_memhole in get_num_dumpable_cyclic is necessary.
>
> Signed-off-by: Baoquan He <bhe at redhat.com>
> ---
> makedumpfile.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/makedumpfile.c b/makedumpfile.c
> index 3884aa5..760bfd1 100644
> --- a/makedumpfile.c
> +++ b/makedumpfile.c
> @@ -5588,6 +5588,8 @@ get_num_dumpable_cyclic(void)
> mdf_pfn_t pfn, num_dumpable=0;
> struct cycle cycle = {0};
>
> + pfn_memhole = info->max_mapnr;
> +
> for_each_cycle(0, info->max_mapnr, &cycle)
> {
> if (!exclude_unnecessary_pages_cyclic(&cycle))
> --
> 1.8.4.2
More information about the kexec
mailing list