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
| ||
|
Message-ID: <20180415004134.GB15294@bombadil.infradead.org> Date: Sat, 14 Apr 2018 17:41:34 -0700 From: Matthew Wilcox <willy@...radead.org> To: "Theodore Y. Ts'o" <tytso@....edu>, Alexey Dobriyan <adobriyan@...il.com>, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: repeatable boot randomness inside KVM guest On Sat, Apr 14, 2018 at 06:44:19PM -0400, Theodore Y. Ts'o wrote: > What needs to happen is freelist should get randomized much later in > the boot sequence. Doing it later will require locking; I don't know > enough about the slab/slub code to know whether the slab_mutex would > be sufficient, or some other lock might need to be added. Could we have the bootloader pass in some initial randomness?
Powered by blists - more mailing lists