| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <18170.44782.134750.907938@alkaid.it.uu.se> Date: Wed, 26 Sep 2007 21:11:42 +0200 From: Mikael Pettersson <mikpe@...uu.se> To: "Ulrich Drepper" <drepper@...il.com> Cc: "John Z. Bohach" <jzb2@...orsyst.com>, linux-kernel@...r.kernel.org Subject: Re: __kernel_vsyscall () hangs in SIGCHLD handler Ulrich Drepper writes: > On 9/26/07, John Z. Bohach <jzb2@...orsyst.com> wrote: > > Is there some reason that syslog() sleeps in __kernel_vsyscall() when > > invoked from a signal handler? > > Only very few functions are allowed to be called from signal handlers. > This is clearly spelled out in the POSIX spec. Section XSH 2.4.3 > lists the allowed functions. syslog of course is not on it. The Linux kernel itself imposes no restrictions on what you can do in user-space signal handlers. However, user-space is a different story. The interrupted thread may have held a lock, in which case calling code from the signal handler that tries to take the same lock may result in a deadlock. Or the thread may be been in the process of updating some private data, in which case calling code from the signal handler that tries to access that data may result in data corruption. And then there's libc which may wrap your signal handler with code doing unspecified libc magic. And so on, the possibilities for failure are endless :-) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists