From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: NACK on shift-MM_COPY_SEGMENTS for API change
Date: Fri, 06 May 2005 13:04:43 +0200 [thread overview]
Message-ID: <427B4F4B.5040909@fujitsu-siemens.com> (raw)
In-Reply-To: <200505051214.45279.blaisorblade@yahoo.it>
Blaisorblade wrote:
> I understand the purpose of the patch; however, without any mention about the
> effects (which would be IMHO bad) we no more copy LDT segments on fork/clone,
> which is bad.
No. The patch shifts code only, but AFAICS it doesn't alter the bahavior of UML/i386.
If it does, that would be a bug in the patch!
>
> The patch moves that to the call of modify_ldt, but that's an hack, since
> currently it's perfectly legitimate that a child uses the father's LDT,
> though maybe uncommon.
No. Let's read the code before and after the change:
Before the change, father's LDT is copied in new_mm() using MM_COPY_SEGMENTS.
new_mm() only has one caller, which is init_new_context_skas().
After the change, father's LDT is copied in init_new_ldt(), again
using MM_COPY_SEGMENTS.
init_new_ldt() also has exactly one caller, which again is init_new_context_skas().
In both cases, copying is done only, if /proc/mm is available.
So, nothing in the behavior is changed, but the code is shifted to arch-specific
files.
>
> It would be better to move LDT copying to an arch-specific helper, defaulting
> to null (i.e. an empty inline) and defined only for i386 and x86-64 (even the
> same def. is ok, probably).
Yeah. init_new_ldt() exactly *is* such a arch-specific helper.
In UML/s390, this is a NOOP.
BTW: my UML/i386 uses a libc, that depends on modify_ldt() to manage the TLS.
If UML doesn't copy the LDT, this system crashes. And it works fine with the
changes!
Regards,
Bodo
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-05-06 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 10:14 [uml-devel] NACK on shift-MM_COPY_SEGMENTS for API change Blaisorblade
2005-05-06 11:04 ` Bodo Stroesser [this message]
2005-05-07 15:28 ` [uml-devel] " Blaisorblade
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=427B4F4B.5040909@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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