linux-kernel - Re: [PATCH] um: Fix to call read_initrd after init

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]

Message-Id: <20170428070414.50ace979df068df258ba92ce@kernel.org>
Date:   Fri, 28 Apr 2017 07:04:14 +0900
From:   Masami Hiramatsu <mhiramat@...nel.org>
To:     Richard Weinberger <richard@....at>
Cc:     Jeff Dike <jdike@...toit.com>,
        user-mode-linux-devel@...ts.sourceforge.net,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] um: Fix to call read_initrd after init_bootmem

Hi Richard,

On Thu, 27 Apr 2017 15:53:25 +0200
Richard Weinberger <richard@....at> wrote:

> Masami,
> 
> Am 27.04.2017 um 05:15 schrieb Masami Hiramatsu:
> > Since read_initrd() invokes alloc_bootmem() for allocating
> > memory to load initrd image, it must be called after init_bootmem.
> > 
> > This makes read_initrd() called directly from setup_arch()
> > after init_bootmem() and mem_total_pages().
> 
> Thanks for fixing this! Did you figure since when this is broken?
> I think that should go into -stable.

Thank you for quick response!
As far as I can see, v4.9 kernel has this issue, but v4.4 is OK.
Let me bisect it.

Thank you,

> 
> Thanks,
> //richard


-- 
Masami Hiramatsu <mhiramat@...nel.org>