From: Thomas Gleixner <tglx@linutronix.de>
To: Dave Jiang <dave.jiang@intel.com>
Cc: mingo@redhat.com, hpa@zytor.com, keescook@chromium.org,
bhe@redhat.com, linux-nvdimm@ml01.01.org, x86@kernel.org,
david@fromorbit.com, linux-kernel@vger.kernel.org,
dan.j.williams@intel.com
Subject: Re: [PATCH v6] x86: fix kaslr and memmap collision
Date: Wed, 11 Jan 2017 13:00:24 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1701111246400.3579@nanos> (raw)
In-Reply-To: <148407086864.34638.4228724339196415751.stgit@djiang5-desk3.ch.intel.com>
On Tue, 10 Jan 2017, Dave Jiang wrote:
> +unsigned long simple_strtoul(const char *cp, char **endp, unsigned int base);
> +long simple_strtol(const char *cp, char **endp, unsigned int base);
What are those functions for? They are not used in that patch at all.
> +static void mem_avoid_memmap(void)
> +{
> + char arg[128];
> + int rc = 0;
What's the point of defining this variable here and zero initializing it?
> + /* see if we have any memmap areas */
Sentences start with an upper case letter. Everywhere!
> + if (cmdline_find_option("memmap", arg, sizeof(arg)) > 0) {
You can spare an indentation level by just returning when the search fails.
> + int i = 0;
> + char *str = arg;
> +
> + while (str && (i < MAX_MEMMAP_REGIONS)) {
for (i = 0; str && (i < MAX_MEMMAP_REGIONS); i++) {
Please.
> + unsigned long long start, size;
> + char *k = strchr(str, ',');
> +
> + if (k)
> + *k++ = 0;
> +
> + rc = parse_memmap(str, &start, &size);
> + if (rc < 0)
> + break;
> + str = k;
> + /* a usable region that should not be skipped */
> + if (size == 0)
> + continue;
> +
> + mem_avoid[MEM_AVOID_MEMMAP_BEGIN + i].start = start;
> + mem_avoid[MEM_AVOID_MEMMAP_BEGIN + i].size = size;
So this makes no sense. You parse start/size as unsigned long long and
then store it in an unsigned long. Works on 64bit, but on 32bit this is
just wrong:
Assume a memmap above 4G, which then will create a avoid region below 4G
due to truncation to unsigned long.
Thanks,
tglx
next prev parent reply other threads:[~2017-01-11 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 17:56 Dave Jiang
2017-01-10 19:02 ` Kees Cook
2017-01-11 3:52 ` Baoquan He
2017-01-11 12:00 ` Thomas Gleixner [this message]
2017-01-11 17:59 ` Dave Jiang
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=alpine.DEB.2.20.1701111246400.3579@nanos \
--to=tglx@linutronix.de \
--cc=bhe@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=david@fromorbit.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®