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  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:   Wed, 13 Feb 2019 09:54:15 -0800
From:   Christoph Hellwig <>
To:     Mike Rapoport <>
Cc:     Christoph Hellwig <>,
        Anup Patel <>,
        Palmer Dabbelt <>,
        Albert Ou <>,
        Atish Patra <>,
        Paul Walmsley <>,
        "" <>,
        "" <>,
        Laura Abbott <>,
        CHANDAN VN <>,
        Will Deacon <>
Subject: Re: [PATCH v4 6/6] RISC-V: Free-up initrd in free_initrd_mem()

On Wed, Feb 13, 2019 at 09:38:36AM +0200, Mike Rapoport wrote:
> memblock_free() is has no real effect at this point, no idea why arm64
> calls it.

Looks like the call was added fairly recently by:

commit 05c58752f9dce11e396676eb731a620541590ed0
Author: CHANDAN VN <>
Date:   Mon Apr 30 09:50:18 2018 +0530

    arm64: To remove initrd reserved area entry from memblock

which claims it is to work around the initrd being displayed in

I really think we need to have common behavior there - either do this
for all architectures or none.  I've just sent a series that
consolidates all but a handful of the free_initrd_mem, so implementing
any common behavior on top of that would be good.

Powered by blists - more mailing lists