From: Linus Torvalds <torvalds@osdl.org>
To: Rik van Riel <riel@redhat.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] prevent NULL mmap in topdown model
Date: Wed, 18 May 2005 15:41:47 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0505181540060.18337@ppc970.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0505181714330.3645@chimarrao.boston.redhat.com>
On Wed, 18 May 2005, Rik van Riel wrote:
>
> On Wed, 18 May 2005, Arjan van de Ven wrote:
> > On Wed, 2005-05-18 at 15:57 -0400, Rik van Riel wrote:
> > > This (trivial) patch prevents the topdown allocator from allocating
> > > mmap areas all the way down to address zero. It's not the prettiest
> > > patch, so suggestions for improvement are welcome ;)
> >
> > it looks like you stop at brk() time.. isn't it better to just stop just
> > above NULL instead?? Gives you more space and is less of an artificial
> > barrier..
>
> Firstly, there isn't much below brk() at all.
Guaranteed? What about executables that have fixed code addresses?
Sounds like a dubious approach, in other words.
If you want to, you could make the "how low do you go" thing be an
rlimit-like thing, but I really doubt "brk" makes much sense as the limit.
Linus
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-05-18 22:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 19:57 Rik van Riel
2005-05-18 20:38 ` Arjan van de Ven
2005-05-18 21:16 ` Rik van Riel
2005-05-18 22:41 ` Linus Torvalds [this message]
2005-05-18 22:39 ` Linus Torvalds
2005-05-19 2:25 ` Rik van Riel
2005-05-19 2:47 ` Linus Torvalds
2005-05-19 6:46 ` Chris Wright
2005-05-19 8:15 ` Arjan van de Ven
2005-05-19 8:23 ` Chris Wright
2005-05-29 21:16 ` Greg Stark
2005-05-31 16:56 ` Chris Wright
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=Pine.LNX.4.58.0505181540060.18337@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
/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