This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Wed, Jun 03, 2015 at 06:42:28PM -0300, Alexandre Oliva wrote: > I guess it depends on what is meant by "IE variable". > > I meant it as a TLS variable defined as part of the initial module set, > i.e., the main executable and the transitive closure of its > dependencies. > > Now, if you understood it as a variable declared with the initial-exec > tls_model attribute, I apologize for the confusion. OK, that's what I thought. And I also understand now what your fix attempts to do and I agree that is a better and more general approach. > The case to worry about is a static executable, that for whatever reason > doesn't get these variables linked in, but that dlopens some library > that depends on libc.so, which then brings these variables into the > running image. If libc.so had these variables as IE, this dlopen could > fail. This seems to make a case for not having any variables in libc.so as IE, yet a number of them already are. Siddhesh
Attachment:
pgpjMeYtOo_bf.pgp
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |