Date: Fri, 15 Apr 2016 12:14:22 -0700 From: Kees Cook <keescook@...omium.org> To: Ingo Molnar <mingo@...nel.org> Cc: Yinghai Lu <yinghai@...nel.org>, Baoquan He <bhe@...hat.com>, Ard Biesheuvel <ard.biesheuvel@...aro.org>, Matt Redfearn <matt.redfearn@...tec.com>, "x86@...nel.org" <x86@...nel.org>, "H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>, Vivek Goyal <vgoyal@...hat.com>, Andy Lutomirski <luto@...nel.org>, lasse.collin@...aani.org, Andrew Morton <akpm@...ux-foundation.org>, Dave Young <dyoung@...hat.com>, "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v5 05/21] x86, boot: Calculate decompression size during boot not build On Fri, Apr 15, 2016 at 1:12 AM, Ingo Molnar <mingo@...nel.org> wrote: > > * Kees Cook <keescook@...omium.org> wrote: > >> From: Yinghai Lu <yinghai@...nel.org> >> >> Currently z_extract_offset is calculated in boot/compressed/mkpiggy.c. > > What is the high level meaning of z_extract_offset? I cannot tell without reading > the code - and the point of changelogs is for them to be readable without having > to read the code. I'll clarify it in the changelog. (FWIW, it's the offset into the extraction buffer where it's safe to put the data-to-be-extracted). > The rest of the changelog is pretty good. Thanks! -Kees -- Kees Cook Chrome OS & Brillo Security
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.