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
| ||
|
Date: Tue, 12 Feb 2019 11:37:34 +0100 From: Andreas Schwab <schwab@...e.de> To: Anup Patel <anup@...infault.org> Cc: Christoph Hellwig <hch@...radead.org>, Anup Patel <Anup.Patel@....com>, Palmer Dabbelt <palmer@...ive.com>, Albert Ou <aou@...s.berkeley.edu>, "linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>, Atish Patra <Atish.Patra@....com>, Paul Walmsley <paul.walmsley@...ive.com>, "linux-riscv\@lists.infradead.org" <linux-riscv@...ts.infradead.org> Subject: Re: [PATCH v2 6/6] RISC-V: Implement keepinitrd kernel parameter On Feb 12 2019, Anup Patel <anup@...infault.org> wrote: > So in case of initrd we might not want to free-up the RAM but > we can certainly free-up in case of initramfs. But the default should be keepinitrd=0, shoudn't it? Andreas. -- Andreas Schwab, SUSE Labs, schwab@...e.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
Powered by blists - more mailing lists