The intent of your change is to get the printk for each thread, right? I don't really see the point. The thread that actually had the fault will dequeue a non-SIGKILL signal and report its status. We only need one thread per signal to the print-out. Hmm. I see that non-coredump signals that hit the optimized fatal case in __group_complete_signal will cause every thread to have a pending SIGKILL. So that will be seen first and prevent the print-out. So that's what you intend to change? I'm not sure print-fatal-signals was really ever intended for non-coredump signals. It doesn't seem like it would be all that useful. It's probably even undesireable for every normal C-c killing something to cause a printk. Thanks, Roland --
| Arjan van de Ven | [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in |
| Tilman Schmidt | git guidance |
| Vu Pham | Re: [Scst-devel] Integration of SCST in the mainstream Linux kernel |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| David Miller | Re: Git and GCC |
| Mike | I don't want the .git directory next to my code. |
| Steffen Prohaska | merge vs rebase: Is visualization in gitk the only problem? |
| David Kastrup | What is the idea for bare repositories? |
| Richard Stallman | Real men don't attack straw men |
| GVG GVG | ssh_exchange_identification: Connection closed by remote host |
| Falk Brockerhoff | ftp-proxy and no route to host issue |
| Pieter Verberne | Remove escape characters from file |
| Chuck Lever | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Stefan Richter | Re: [GIT]: Networking |
| jamal | Re: [LARTC] ifb and ppp |
