All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Arostegui Ramirez <manuel@todo-linux.com>
To: Han Boetes <han@mijncomputer.nl>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: new kernel bug
Date: Sat, 12 Jun 2004 17:08:12 +0200	[thread overview]
Message-ID: <200406121708.12827.manuel@todo-linux.com> (raw)
In-Reply-To: <20040612150851.GC5922@boetes.org>

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


  reply	other threads:[~2004-06-12 15:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-12  9:59 new kernel bug Manuel Arostegui Ramirez
2004-06-12 12:33 ` Kalin KOZHUHAROV
2004-06-12 12:42   ` Manuel Arostegui Ramirez
2004-06-12 13:37     ` David Connolly
2004-06-12 15:08     ` Han Boetes
2004-06-12 15:08       ` Manuel Arostegui Ramirez [this message]
2004-06-14 13:58 ` Local DoS attack on i386 (was: new kernel bug) Gianni Tedesco
2004-06-14 14:05   ` Gianni Tedesco
2004-06-14 14:08   ` Manuel Arostegui Ramirez
2004-06-14 14:20   ` Nuno Monteiro
2004-06-14 14:59     ` Manuel Arostegui Ramirez
2004-06-15  4:34     ` Local DoS attack on i386 Andre Tomt
  -- strict thread matches above, loose matches on Subject: below --
2004-06-12 12:40 new kernel bug stian
2004-06-12 12:48 ` Manuel Arostegui Ramirez
2004-06-12 13:44 stian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200406121708.12827.manuel@todo-linux.com \
    --to=manuel@todo-linux.com \
    --cc=han@mijncomputer.nl \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.