From: John Reiser <jreiser@BitWagon.com>
To: uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] should there be os_clone() analogous to os_getpid() ?
Date: Sat, 08 Dec 2007 20:24:57 -0800 [thread overview]
Message-ID: <475B6E19.6040200@BitWagon.com> (raw)
In source file arch/um/os-Linux/process.c there is a warning:
-----
/* Don't use the glibc version, which caches the result in TLS. It misses some
* syscalls, and also breaks with clone(), which does not unshare the TLS.
*/
int os_getpid(void)
-----
I see no os_clone(), yet the glibc clone() does the same caching of pid in
ThreadLocalStorage [TLS], and the TLS still may be shared. If nobody reads
glibc's shared TLS slot for PID then an actual bug will be avoided. However,
it is unsafe to leave such a tempting pitfall. Also, if you are ptrace()ing
through a glibc clone(), then in many cases you will see syscall(__NR_getpid)
*from glibc* immediately following! There is an "extra" getpid()
that the tracking logic might not expect. So it seems to me that
there should be an os_clone() that refrains from fiddling with getpid.
[Unfortunately os_clone() is not so simple as os_getpid().]
The clone() we're talking about here is _not_ the bare syscall:
-----
_syscall5(int, clone, int, flags, void *, child_stack,
int *, parent_tidptr, struct user_desc *, newtls,
int *, child_tidptr)
-----
but rather the C-language interface:
-----
int clone(int (*fn)(void *), void *child_stack,
int flags, void *arg, ...
/* pid_t *pid, struct user_desc *tls, pid_t *ctid */ );
-----
which is declared in arch/um/include/kern.h and referenced in
arch/um/drivers/ubd_user.c
arch/um/kernel/tt/tracer.c
arch/um/os/tt.c
arch/um/os/start_up.c
arch/um/os/skas/process.c
This clone() is implemented by glibc, and at runtime lives in the shared
library /lib/libc.so.6.
Not only that, but some versions of glibc for x86 use "int $0x80" directly
only for the __NR_clone call. They use "ENTER_KERNEL" for the getpid(),
which in some cases (such as Fedora 7 and 8, but not Ubuntu 7.04) expands to
"call *%gs:nnnnn" which points at "sysenter; ret".
--
John Reiser, jreiser@BitWagon.com
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2007-12-09 4:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 4:24 John Reiser [this message]
2007-12-09 15:10 ` [uml-devel] should there be os_clone() analogous to os_getpid() ? Jeff Dike
2007-12-09 20:58 ` John Reiser
2007-12-10 17:09 ` 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=475B6E19.6040200@BitWagon.com \
--to=jreiser@bitwagon.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