public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@karaya.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] Allow UML kernel to run in a separate host address space
Date: Sun, 29 Dec 2002 00:12:51 -0500	[thread overview]
Message-ID: <200212290512.AAA05609@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Sat, 28 Dec 2002 20:13:44 PST." <Pine.LNX.4.44.0212282010080.2029-100000@home.transmeta.com>

torvalds@transmeta.com said:
> But that is an address space that it should already has access to
> through,  since it created it in the first place (ie it would fall
> under the normal  "sys_mm_indirect()" case). 

Yes, and so it doesn't fall under ptrace.  I think we're in violent agreement
here.

> The thing that I _really_ don't want to have is soem uncontrolled way
> to  generate accesses to existing "struct mm_struct"s, since that is
> really  dangerous from a security standpoint. 

Fine by me.  UML has no need for manipulating pre-existing address spaces.

> We could have a PTRACE_GET_MM_FD kind of thing for ptrace (and then
> the  gdb/tracer can use that to create mappings in the process), but
> the reason  I want that "hook" to be through ptrace itself is simply
> that it's a known  interface to control other unrelated processes.
>
> So if you create the MM's yourself, you can use the indirection
> directly.  But if you want to control your children or unrelated
> processes, you use  ptrace to get the hook.  

Yup.  As far as UML is concerned, this is all fine.  It has no need of
a PTRACE_GET_MM_FD since it creates all address spaces itself, but other
tools might.

				Jeff


  reply	other threads:[~2002-12-29  5:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-28 15:47 [PATCH] Allow UML kernel to run in a separate host address space Jeff Dike
2002-12-28 19:34 ` Linus Torvalds
2002-12-28 20:24   ` Jeff Dike
2002-12-28 20:50     ` Linus Torvalds
2002-12-28 23:37       ` Jeff Dike
2002-12-29  4:13         ` Linus Torvalds
2002-12-29  5:12           ` Jeff Dike [this message]
2002-12-29  0:59       ` Daniel Jacobowitz
2002-12-29  4:03     ` Jeremy Fitzhardinge
2002-12-29  5:12       ` Jeff Dike
  -- strict thread matches above, loose matches on Subject: below --
2002-12-17 23:24 Jeff Dike

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=200212290512.AAA05609@ccure.karaya.com \
    --to=jdike@karaya.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@transmeta.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