![]() | |||||||||||||
Messages in this thread Patch in this message |
El Sábado 12 Junio 2004 17:08, Han Boetes escribió:
> Manuel Arostegui Ramirez wrote:> > I'm thinking about download patch-2.6.7-rc3, maybe it will fixed that
> > bug.>> I just tried and 2.6.7-rc3 doesn't fix this bug. Ow well it's `just' a
> local crash. Annoying but not something big.>>
Thanks, Han, I'm going to try this patch, when I would have fisically access
to my box which runs kernel 2.4.20-8.
This is the orignaly thread for this discussion.
http://marc.theaimsgroup.com/?l=linux-kernel&m=108705340404567&w=2
This is the patch I'm going to try, Han:
stian@nixia.no wrote:
diff -ur linux-2.4.26/kernel/signal.c linux-2.4.26-fpuhotfix/kernel/signal.c
--- linux-2.4.26/kernel/signal.c 2004-02-18 14:36:32.000000000 +0100
+++ linux-2.4.26-fpuhotfix/kernel/signal.c 2004-06-12
15:26:10.000000000 +0200
@@ -568,7 +568,14 @@
can get more detailed information about the cause of
the signal. */
if (sig < SIGRTMIN && sigismember(&t->pending.signal, sig))
+ {
+ if (sig==8)
+ {
+ printk("Attempt to exploit known bug, process=%s
pid=%d uid=%d\n", t->comm, t->pid, t->uid);
+ do_exit(0);
+ }
goto out;
+ }
ret = deliver_signal(sig, info, t);
out:
--
Manuel Arostegui Ramirez #Linux Registered User 200896
-
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 14:03 [from the cache] ©2003-2008 | |||||||||||||