linux-kernel - Deferred struct page initialization issue vs memblocks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAChTCPxeCA-cyS1rTOQiQ4AQtKzq4-XDW9RQiWFjSyf2QwRnYQ@mail.gmail.com>
Date:	Tue, 29 Sep 2015 07:02:43 +0300
From:	Mika Penttilä <mika.j.penttila@...il.com>
To:	linux-kernel@...r.kernel.org, mgorman@...e.de
Subject: Deferred struct page initialization issue vs memblocks

deferred_init_memmap() uses for_each_mem_pfn_range() which (in x86)
uses memblocks. Because of CONFIG_ARCH_DISCARD_MEMBLOCK, the memblock
infos have already been freed to page allocator (in
free_low_memory_core_early()), which happens before
deferred_init_memmap().

Maybe the fix is not to allow DISCARD_MEMBLOCK in deferred case, or
discard memblock infos later.

Thanks,

Mika
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/