From: Peter Zijlstra <peterz@infradead.org>
To: Hugh Dickins <hugh.dickins@tiscali.co.uk>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
David Miller <davem@davemloft.net>, Ollie Wild <aaw@google.com>,
Rik van Riel <riel@redhat.com>,
viro@ftp.linux.org.uk, linux-arch@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCHSET] mremap/mmap mess
Date: Wed, 09 Dec 2009 13:21:42 +0100 [thread overview]
Message-ID: <1260361302.5489.372.camel@laptop> (raw)
In-Reply-To: <Pine.LNX.4.64.0912091041250.23659@sister.anvils>
On Wed, 2009-12-09 at 11:43 +0000, Hugh Dickins wrote:
> On Tue, 8 Dec 2009, Al Viro wrote:
> > On Tue, Dec 08, 2009 at 01:08:02PM -0800, David Miller wrote:
> > > From: Hugh Dickins <hugh.dickins@tiscali.co.uk>
> > > Date: Tue, 8 Dec 2009 13:03:30 +0000 (GMT)
> Would it make sense to build up argv and env of execee on the execer's
> user stack (below user's sp ("below" assuming topdown stack))?
> > >
> > > > That would impose some (unacceptable?) limits, and require some funny
> > > > code to migrate the pages over to the new mm later (instead of
> > > > relocating within the new mm as we do now).
> > >
> > > I think this approach would create new failure cases that don't exist
> > > now. Whether that's acceptable or not is another issue.
>
> David: Yes, that's one of my fears too - I don't think
> rlimits would pose any new problem, but building up the argv+env below
> sp on the execer's userstack would be in danger of colliding with the
> vma below if the space allowed to that userstack is too small. We can
> say "sorry, you left too little space for your userstack", but it's
> still a regression. My other big fear is this: that it's such a simple
> and obvious way to do it, that it has probably been ruled out for very
> good reasons in the past.
Vague memories, but here goes..
/me ponders.. doesn't the binfmt engine cruft need the args in place in
order to execute?
That is, IIRC the problem is that you need to have the argc/env in place
for the binfmt engine thing, and need to have ran the binfmt engine
thing before you know the personality.
As to your idea, if that were feasible we could do without the copy and
simply steal the pages directly from the old mm.
next prev parent reply other threads:[~2009-12-09 12:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 19:08 [RFC][PATCHSET] mremap/mmap mess Al Viro
2009-12-05 19:08 ` Al Viro
2009-12-05 20:44 ` Linus Torvalds
2009-12-05 23:01 ` Al Viro
2009-12-05 23:58 ` Russell King
2009-12-06 17:22 ` Hugh Dickins
2009-12-06 18:00 ` Linus Torvalds
2009-12-07 3:58 ` Al Viro
2009-12-07 18:58 ` Hugh Dickins
2009-12-07 18:58 ` Hugh Dickins
2009-12-07 19:30 ` Al Viro
2009-12-07 20:05 ` Hugh Dickins
2009-12-07 20:05 ` Hugh Dickins
2009-12-08 6:07 ` Al Viro
2009-12-08 11:42 ` Hugh Dickins
2009-12-08 13:03 ` Hugh Dickins
2009-12-08 21:08 ` David Miller
2009-12-08 22:06 ` Al Viro
2009-12-09 11:43 ` Hugh Dickins
2009-12-09 12:21 ` Peter Zijlstra [this message]
2009-12-09 12:21 ` Peter Zijlstra
2009-12-09 13:12 ` Hugh Dickins
2009-12-09 13:37 ` Peter Zijlstra
2009-12-09 13:24 ` Al Viro
2009-12-09 13:39 ` Peter Zijlstra
2009-12-09 13:46 ` Al Viro
2009-12-09 14:36 ` Hugh Dickins
2009-12-09 15:12 ` Linus Torvalds
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=1260361302.5489.372.camel@laptop \
--to=peterz@infradead.org \
--cc=aaw@google.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=viro@ftp.linux.org.uk \
/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