On Sat, Jul 15, 2017 at 5:42 AM, Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> wrote: > (+ Mark, Will, Catalin) > > On 15 July 2017 at 01:38, Kees Cook <keescook@xxxxxxxxxxxx> wrote: >> Document then /chosen/kaslr-seed property (and its interaction with the >> EFI_RNG_PROTOCOL API). >> >> Signed-off-by: Kees Cook <keescook@xxxxxxxxxxxx> >> --- >> Documentation/devicetree/bindings/chosen.txt | 22 ++++++++++++++++++++-- >> 1 file changed, 20 insertions(+), 2 deletions(-) >> > > For the textual changes: > > Acked-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> > > *However*, documenting the /chosen/kaslr-seed property promotes it > from a stub<->kernel private interface to an external ABI between the > kernel and the bootloader, and we need to reach agreement on whether > doing so is desirable first IMHO. > Oh! I thought that was the point (having a bootloader provide kaslr entropy). And that in the EFI case, it was the stub doing it. -Kees -- Kees Cook Pixel Security -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
