Re: + mm-page_alloc-fix-memmap_init_zone-pageblock-alignment.patch added to -mm tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Mar 3, 2018 at 1:41 AM,  <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> diff -puN mm/page_alloc.c~mm-page_alloc-fix-memmap_init_zone-pageblock-alignment mm/page_alloc.c
> --- a/mm/page_alloc.c~mm-page_alloc-fix-memmap_init_zone-pageblock-alignment
> +++ a/mm/page_alloc.c
> @@ -5359,9 +5359,14 @@ void __meminit memmap_init_zone(unsigned
>                         /*
>                          * Skip to the pfn preceding the next valid one (or
>                          * end_pfn), such that we hit a valid pfn (or end_pfn)
> -                        * on our next iteration of the loop.
> +                        * on our next iteration of the loop. Note that it needs
> +                        * to be pageblock aligned even when the region itself
> +                        * is not. move_freepages_block() can shift ahead of
> +                        * the valid region but still depends on correct page
> +                        * metadata.
>                          */
> -                       pfn = memblock_next_valid_pfn(pfn, end_pfn) - 1;
> +                       pfn = (memblock_next_valid_pfn(pfn, end_pfn) &
> +                                       ~(pageblock_nr_pages-1)) - 1;

Did you revert the first patch of the series for some reason?

>  #endif
>                         continue;
>                 }
> _
>
> Patches currently in -mm which might be from neelx@xxxxxxxxxx are
>
> mm-memblock-hardcode-the-end_pfn-being-1.patch

But it seems listed here...

> mm-page_alloc-fix-memmap_init_zone-pageblock-alignment.patch
>



[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]