This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
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 Tue, Jun 22, Jakub Jelinek wrote: > On Tue, Jun 22, 2004 at 11:50:59PM +0200, Thorsten Kukuk wrote: > > > > Hi, > > > > I got the following test program. I know, it is very ugly and there > > are a lot of things somebody should not do, but this is something > > what programs like sshd are doing. > > Then they should be fixed. Neither syslog, nor printf, nor fflush > are supposed to be async-signal safe, nor they actually are in glibc. Yes, but the problem is: Nearly every daemon on a Linux system is calling syslog() in a signal handler and it seems to be very easy to deadlock them on every Linux system running glibc/NPTL. While there seems to be no other system with the same problem. Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE Linux AG Maxfeldstr. 5 D-90409 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |