Messages in this thread | | | Subject | Re: light weight user level semaphores | Date | Thu, 19 Apr 2001 18:12:42 +0100 (BST) | From | Alan Cox <> |
| |
> > libc is entitled to, and most definitely does exactly that. Take a look at > > things like gethostent, getpwent etc etc. > > Ehh.. I will bet you $10 USD that if libc allocates the next file > descriptor on the first "malloc()" in user space (in order to use the > semaphores for mm protection), programs _will_ break. > > You want to take the bet?
Its not normally a good idea to take a Linus bet, but this time Im obviously missing something. fd0-2 will be passed in (and if not then shit already happens - see old bugtraq on the matter for setuid apps, glibc bugs)
So the C library gets fd 3 My first fopen gets fd 4.
That can already happen and isnt new. Several profiling libraries on Unix have precisely this effect already. They dynamic link/loader will also open file handles to do mmaps although generally you wont see those as they are closed again after mapping.
Internationalisation code in glibc will also open and map tables during startup
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |