linux-kernel - Re: [PATCH] mm, meminit: Serially initialise deferred memory if trace_buf

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 16 Nov 2017 09:54:33 +0100
From:   Michal Hocko <mhocko@...nel.org>
To:     YASUAKI ISHIMATSU <yasu.isimatu@...il.com>
Cc:     Mel Gorman <mgorman@...hsingularity.net>,
        Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org, koki.sanagi@...fujitsu.com
Subject: Re: [PATCH] mm, meminit: Serially initialise deferred memory if
 trace_buf_size is specified

On Wed 15-11-17 14:17:52, YASUAKI ISHIMATSU wrote:
> Hi Michal and Mel,
> 
> To reproduce the issue, I specified the large trace buffer. The issue also occurs with
> trace_buf_size=12M and movable_node on 4.14.0.

This is still 10x more than the default. Why do you need it in the first
place? You can of course find a size that will not fit into the initial
memory but I am questioning why do you want something like that during
early boot in the first place.

The whole deferred struct page allocation operates under assumption
that there are no large page allocator consumers that early during
the boot process. If this assumption is not correct then we probably
need a generic way to describe this. Add-hoc trace specific thing is
far from idea, imho. If anything the first approach to disable the
deferred initialization via kernel command line option sounds much more
appropriate and simpler to me.
-- 
Michal Hocko
SUSE Labs