linux-kernel - RE: [PATCH v2 6/6] RISC-V: Implement keepinitrd kernel parameter

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: <MN2PR04MB606129EF849F6AD914047D388D660@MN2PR04MB6061.namprd04.prod.outlook.com>
Date:   Wed, 13 Feb 2019 06:05:19 +0000
From:   Anup Patel <Anup.Patel@....com>
To:     Christoph Hellwig <hch@...radead.org>
CC:     Anup Patel <anup@...infault.org>,
        Palmer Dabbelt <palmer@...ive.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Atish Patra <Atish.Patra@....com>,
        Albert Ou <aou@...s.berkeley.edu>,
        Paul Walmsley <paul.walmsley@...ive.com>,
        "linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>
Subject: RE: [PATCH v2 6/6] RISC-V: Implement keepinitrd kernel parameter



> -----Original Message-----
> From: Christoph Hellwig [mailto:hch@...radead.org]
> Sent: Wednesday, February 13, 2019 11:25 AM
> To: Anup Patel <Anup.Patel@....com>
> Cc: Christoph Hellwig <hch@...radead.org>; Anup Patel
> <anup@...infault.org>; Palmer Dabbelt <palmer@...ive.com>; linux-
> kernel@...r.kernel.org; Atish Patra <Atish.Patra@....com>; Albert Ou
> <aou@...s.berkeley.edu>; Paul Walmsley <paul.walmsley@...ive.com>;
> linux-riscv@...ts.infradead.org
> Subject: Re: [PATCH v2 6/6] RISC-V: Implement keepinitrd kernel parameter
> 
> On Wed, Feb 13, 2019 at 03:43:06AM +0000, Anup Patel wrote:
> > Sure, the keepinitrd=0 by default so it will always free-up initrd by default.
> > Please look at v3 patchset.
> >
> > Of course, we need separate patch to update documentation of
> keepinitrd.
> 
> No, we need to not just blindly copy what arm did for historic reasons unless
> we have a very good reason of our own.
> 
> In addition to not having a real need for any of this in a new setup, it also is
> duplicated by the retain_initrd parameter which is implemented in generic
> code - and for that the commit message at least has a rationale related to
> kexec:
> 
> https://lkml.org/lkml/2006/12/7/15

Sure, I will re-work this patch to always free-up initrd.

Regards,
Anup