Re: [patch] threading fix, tid-2.5.47-A3

[Luca Barbieri]

--=-ptoHREeIDFMZoJ2YheTO
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

> > You could avoid the additional pointer by letting
> > child_tidptr =3D (!(flags & CLONE_VM) && current->user_tid) ?
> > current->user_tid : parent_tidptr;
>=20
> This doesn't work since it would overwrite the TID field in the calling
> thread's descriptor.
No: for the pthread_create case you would pass the pointer to new struct
pthread tid in parent_tidptr, while for fork you would pass the
parameter of cfork as parent_tidptr and child_tidptr would be inherited.

However I don't think that this is a good interface, just a bit better
than having two flags and a single pointer.

--=-ptoHREeIDFMZoJ2YheTO
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA92KRxdjkty3ft5+cRAohTAJ4gttuImeeSB9ivuYdkb5EZSCuWdACfUskO
D8qgG0tqSHw5g6W4r+tfIwY=
=Zra3
-----END PGP SIGNATURE-----

--=-ptoHREeIDFMZoJ2YheTO--