bionic/libc
Jack Ren d8bc6e7119 bionic: Fix wrong kernel_id in pthread descriptor after fork()
After forking, the kernel_id field in the phtread_internal_t returned by pthread_self()
is incorrect --- it's the tid from the parent, not the new tid of the
child.

The root cause is that: currently the kernel_id is set by
_init_thread(), which is called in 2 cases:
(1) called by __libc_init_common(). That happens when the execv( ) is
called after fork( ). But when the zygote tries to fork the android
application, the child application doesn't call execv( ), instread, it
tries to call the Java main method directly.
(2) called by pthread_create(). That happens when a new thread is
created.

For the lead thread which is the thread created by fork(), it should
call execv() but it doesn't, as described in (1) above. So its kernel_id
will inherit the parent's kernel_id.

Fixed it in this patch.

Change-Id: I63513e82af40ec5fe51fbb69456b1843e4bc0fc7
Signed-off-by: Chenyang Du <chenyang.du@intel.com>
Signed-off-by: Jack Ren <jack.ren@intel.com>
Signed-off-by: Bruce Beare <bruce.j.beare@intel.com>
2012-03-12 23:14:56 +08:00
..
arch-arm libc: Define new symbol visibility macros 2012-01-31 22:19:09 +01:00
arch-x86 bionic/x86: fix one potential deadlock in __set_tls() 2012-02-23 17:37:58 +08:00
bionic bionic: Fix wrong kernel_id in pthread descriptor after fork() 2012-03-12 23:14:56 +08:00
docs libc: Fix the definition of SIGRTMAX 2010-12-20 15:58:06 +01:00
include Eliminate duplicate constants 2012-02-29 18:43:51 -08:00
inet Fix build. 2011-06-09 13:03:17 -07:00
kernel update stddef.h 2012-02-29 18:43:55 -08:00
netbsd res_send: Avoid spurious close()s and (rare) failure 2012-01-14 11:30:00 +08:00
private bionic: Fix wrong kernel_id in pthread descriptor after fork() 2012-03-12 23:14:56 +08:00
regex Remove compiler warnings when building Bionic. 2010-06-22 17:51:41 -07:00
stdio am 4685acbd: am 9efda5b7: Merge "typo in libc/stdio/wcio.h" 2011-08-03 08:16:37 -07:00
stdlib Enable functional DSO object destruction 2011-07-07 22:51:43 +02:00
string string: Fix wrong comparison semantics 2011-12-05 18:37:10 -08:00
tools remove obsolete SuperH support 2012-01-31 20:28:23 +01:00
tzcode am ac56f5ca: Merge "strftime: Use snprintf() instead of sprintf()" 2011-06-23 06:13:53 -07:00
unistd execvp: bcopy() is deprecated. Use memcpy() instead 2012-01-14 11:22:36 +08:00
wchar wchar.h: improve wchar_t support in Bionic 2010-06-15 07:04:41 -07:00
zoneinfo Upgrade to tzdata2012b. 2012-03-01 23:34:11 -08:00
Android.mk remove obsolete SuperH support 2012-01-31 20:28:23 +01:00
CAVEATS auto import from //depot/cupcake/@135843 2009-03-03 19:28:35 -08:00
Jamfile auto import from //depot/cupcake/@135843 2009-03-03 19:28:35 -08:00
MODULE_LICENSE_BSD auto import from //depot/cupcake/@135843 2009-03-03 19:28:35 -08:00
NOTICE Clean up NOTICE files. 2010-10-19 15:12:40 -07:00
README Add an 's and a . to the bionic/libc README. 2009-07-23 17:41:47 -07:00
SYSCALLS.TXT Clean up the remnants of SuperH support 2012-02-09 15:58:46 -08:00

Welcome to Bionic, Android's small and custom C library for the Android
platform.

Bionic is mainly a port of the BSD C library to our Linux kernel with the
following additions/changes:

- no support for locales
- no support for wide chars (i.e. multi-byte characters)
- its own smallish implementation of pthreads based on Linux futexes
- support for x86, ARM and ARM thumb CPU instruction sets and kernel interfaces

Bionic is released under the standard 3-clause BSD License

Bionic doesn't want to implement all features of a traditional C library, we only
add features to it as we need them, and we try to keep things as simple and small
as possible. Our goal is not to support scaling to thousands of concurrent threads
on multi-processors machines; we're running this on cell-phones, damnit !!

Note that Bionic doesn't provide a libthread_db or a libm implementation.


Adding new syscalls:
====================

Bionic provides the gensyscalls.py Python script to automatically generate syscall
stubs from the list defined in the file SYSCALLS.TXT. You can thus add a new syscall
by doing the following:

- edit SYSCALLS.TXT
- add a new line describing your syscall, it should look like:

   return_type  syscall_name(parameters)    syscall_number

- in the event where you want to differentiate the syscall function from its entry name,
  use the alternate:

   return_type  funcname:syscall_name(parameters)  syscall_number

- additionally, if the syscall number is different between ARM and x86, use:

   return_type  funcname[:syscall_name](parameters)   arm_number,x86_number

- a syscall number can be -1 to indicate that the syscall is not implemented on
  a given platform, for example:

   void   __set_tls(void*)   arm_number,-1


the comments in SYSCALLS.TXT contain more information about the line format

You can also use the 'checksyscalls.py' script to check that all the syscall
numbers you entered are correct. It does so by looking at the values defined in
your Linux kernel headers. The script indicates where the values are incorrect
and what is expected instead.