| 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: <20061118023832.GG13827@flower.upol.cz> Date: Sat, 18 Nov 2006 02:38:32 +0000 From: Oleg Verych <olecom@...wer.upol.cz> To: Folkert van Heusden <folkert@...heusden.com> Cc: LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] emit logging when a process receives a fatal signal On Sat, Nov 18, 2006 at 03:04:13AM +0100, Folkert van Heusden wrote: > > > > I found that sometimes processes disappear on some heavily used system > > > > of mine without any logging. So I've written a patch against 2.6.18.2 > > > > which emits logging when a process emits a fatal signal. > > > Why not to patch default signal handlers in glibc, to have not only > > > stderr, but syslog, or /dev/kmsg copy of fatal messages? > > Afaik when a proces gets shot because of a segfault, also the libraries > > it used are shot so to say. iirc some of the more fatal signals are > > handled directly by the kernel. Kernel sends signals, no doubt. Then, who you think prints that "Killed" or "Segmentation fault" messages in *stderr*? [Hint: libc's default signal handler (man 2 signal).] > Also: what about statically build programs? "-lc" embeds libc in static binary, no? IMHO it's not a lkml issue. Here are many who would say you, that userspace preblems are userspace problems. ____ - 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