From: Baoquan He <bhe@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: mingo@kernel.org, keescook@chromium.org,
linux-kernel@vger.kernel.org, dyoung@redhat.com,
douly.fnst@cn.fujitsu.com, dan.j.williams@intel.com,
hpa@zytor.com, x86@kernel.org
Subject: Re: [PATCH v4 1/3] KASLR: Parse all memmap entries in cmdline
Date: Wed, 10 May 2017 21:11:15 +0800 [thread overview]
Message-ID: <20170510131115.GH21870@x1> (raw)
In-Reply-To: <alpine.DEB.2.20.1705101420260.1979@nanos>
On 05/10/17 at 02:29pm, Thomas Gleixner wrote:
> On Tue, 9 May 2017, Baoquan He wrote:
>
> > In commit:
> >
> > f28442497b5c ("x86/boot: Fix KASLR and memmap= collision")
> >
> > ... the memmap= option is parsed so that KASLR can avoid those reserved
> > regions. It uses cmdline_find_option() to get the value if memmap=
> > is specified, however the problem is that cmdline_find_option() can only
> > find the last entry if multiple memmap entries are provided. This
> > is not correct.
> >
> > In this patch, the whole cmdline will be scanned to search each
>
> Can you please finally stop using this 'This patch does foo', 'In this
> patch' phrases. They are bogus. We already know that this is a patch
> otherwise you wouldn't have sent it.
>
> See Documentation/process/SubmittingPatches.txt
>
> Aside of that can you please use properly written out words instead of
> using random abbreviations in the changelog, e.g. command line instead of
> cmdline?
>
> > memmap, all of them will be parsed and handled.
>
> A proper example would be:
>
> Address this by checking each command line token for a "memmap=" match
> and parse each instance instead of using cmdline_find_option().
Sorry for those mistakes. Will change accordingly when repost.
Thanks
Baoquan
next prev parent reply other threads:[~2017-05-10 13:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 5:57 [PATCH v4 0/3] Handle memmap and mem kernel options in boot stage kaslr Baoquan He
2017-05-09 5:57 ` [PATCH v4 1/3] KASLR: Parse all memmap entries in cmdline Baoquan He
2017-05-10 12:29 ` Thomas Gleixner
2017-05-10 13:11 ` Baoquan He [this message]
2017-05-09 5:57 ` [PATCH v4 2/3] KASLR: Handle memory limit specified by memmap and mem option Baoquan He
2017-05-09 17:39 ` Kees Cook
2017-05-10 0:35 ` Baoquan He
2017-05-12 4:15 ` Masayoshi Mizuma
2017-05-12 5:06 ` Baoquan He
2017-05-09 5:57 ` [PATCH v4 3/3] Documentation/kernel-parameters.txt: Update 'memmap=' option description 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=20170510131115.GH21870@x1 \
--to=bhe@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox