![]() | |||||||||||||
Messages in this thread |
On Friday 09 April 2004 12:11, Nikita V. Youshchenko wrote: > Hello. > > Several days ago I've posted to linux-kernel describing "zombie problem" > related to sigqueue overflow. > > Futher exploration of the problem showed that the reason of the described > behaviour is in user-space. There is a process that blocks a signal and > later receives tons of such signals. This effectively causes sigqueue > overflow. One solution would be to watermark sigqueue and upon reaching high mark, find the process with most signals queued and drop those. This prevents one buggy process, even root-launched, from interfering with non-buggy ones. If low watermark is not reached, find _UID_ which have max # of signals pending, and drop them all. This will work against rogue user trying to DoS box who's careful enough to do it from multiple processes. -- vda - 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/ | ||||||||||||
| Last update: 2005-03-22 13:02 [from the cache] ©2003-2008 | |||||||||||||