From: mingo@kernel.org (Ingo Molnar)
To: linux-arm-kernel@lists.infradead.org
Subject: mm: insure topdown mmap chooses addresses above security minimum
Date: Wed, 25 Sep 2013 19:44:36 +0200 [thread overview]
Message-ID: <20130925174436.GA14037@gmail.com> (raw)
In-Reply-To: <20130925171243.GA7428@tcpepper-desk.jf.intel.com>
* Timothy Pepper <timothy.c.pepper@linux.intel.com> wrote:
> On Wed 25 Sep at 09:30:49 +0200 mingo at kernel.org said:
> > > info.flags = VM_UNMAPPED_AREA_TOPDOWN;
> > > info.length = len;
> > > - info.low_limit = PAGE_SIZE;
> > > + info.low_limit = max(PAGE_SIZE, PAGE_ALIGN(mmap_min_addr));
> > > info.high_limit = mm->mmap_base;
> > > info.align_mask = filp ? get_align_mask() : 0;
> > > info.align_offset = pgoff << PAGE_SHIFT;
> >
> > There appears to be a lot of repetition in these methods - instead of
> > changing 6 places it would be more future-proof to first factor out the
> > common bits and then to apply the fix to the shared implementation.
>
> Besides that existing redundancy in the multiple somewhat similar
> arch_get_unmapped_area_topdown() functions, I was expecting people might
> question the added redundancy of the six instances of:
>
> max(PAGE_SIZE, PAGE_ALIGN(mmap_min_addr));
That redundancy would be automatically addressed by my suggestion.
Thanks,
Ingo
next prev parent reply other threads:[~2013-09-25 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 21:23 mm: insure topdown mmap chooses addresses above security minimum Timothy Pepper
2013-09-24 21:28 ` Russell King - ARM Linux
2013-09-25 7:30 ` Ingo Molnar
2013-09-25 17:12 ` Timothy Pepper
2013-09-25 17:44 ` Ingo Molnar [this message]
2013-09-27 15:39 ` Timothy Pepper
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=20130925174436.GA14037@gmail.com \
--to=mingo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).