From: Borislav Petkov <bp@suse.de>
To: Kees Cook <keescook@chromium.org>
Cc: linux-tip-commits@vger.kernel.org, yinghai@kernel.org,
peterz@infradead.org, brgerst@gmail.com, hpa@zytor.com,
bhe@redhat.com, mingo@kernel.org, torvalds@linux-foundation.org,
tglx@linutronix.de, luto@amacapital.net,
linux-kernel@vger.kernel.org, dvlasenk@redhat.com,
luto@kernel.org, keescook@chromium.org
Subject: Re: [tip:x86/boot] x86/KASLR: Improve comments around the mem_avoid[] logic
Date: Mon, 9 May 2016 10:45:17 +0200 [thread overview]
Message-ID: <20160509084517.GD4107@pd.tnic> (raw)
In-Reply-To: <tip-ed09acde44e301b5c13755ab84821fa44b188b5e@git.kernel.org>
On Fri, May 06, 2016 at 11:36:08PM -0700, tip-bot for Kees Cook wrote:
> Commit-ID: ed09acde44e301b5c13755ab84821fa44b188b5e
> Gitweb: http://git.kernel.org/tip/ed09acde44e301b5c13755ab84821fa44b188b5e
> Author: Kees Cook <keescook@chromium.org>
> AuthorDate: Fri, 6 May 2016 12:44:59 -0700
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitDate: Sat, 7 May 2016 07:38:38 +0200
>
> x86/KASLR: Improve comments around the mem_avoid[] logic
>
> This attempts to improve the comments that describe how the memory
> range used for decompression is avoided. Additionally uses an enum
> instead of raw numbers for the mem_avoid[] indexing.
Just went through the text, looks nice. Thanks for the effort!
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2016-05-09 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 19:44 [PATCH] x86/KASLR: Improve comments around mem_avoid Kees Cook
2016-05-07 6:36 ` [tip:x86/boot] x86/KASLR: Improve comments around the mem_avoid[] logic tip-bot for Kees Cook
2016-05-09 8:45 ` Borislav Petkov [this message]
2016-05-09 8:49 ` Baoquan He
2016-05-09 8:58 ` Borislav Petkov
2016-05-09 9:19 ` Baoquan He
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160509084517.GD4107@pd.tnic \
--to=bp@suse.de \
--cc=bhe@redhat.com \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.