From: Kalin KOZHUHAROV <kalin@ThinRope.net>
To: linux-kernel@vger.kernel.org
Subject: Re: timer + fpu stuff locks my console race
Date: Sat, 12 Jun 2004 22:50:02 +0900 [thread overview]
Message-ID: <40CB0A0A.1010104@ThinRope.net> (raw)
In-Reply-To: <1404.83.109.11.80.1087046920.squirrel@nepa.nlc.no>
stian@nixia.no wrote:
> Forgot to update the diff file after I fixed some bogus stuff. This patch
> file compiles. Please report if it works or not for 2.4.26 (I'm lacking
> that damn Internett connection on my linux box). So much for vaccation.
>
> Stian Skjelstad
>
> 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:
Does this work for 2.6.{6,7} ?
Kalin.
--
||///_ o *****************************
||//'_/> WWW: http://ThinRope.net/
|||\/<"
|||\\ '
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
next prev parent reply other threads:[~2004-06-12 13:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 13:28 timer + fpu stuff locks my console race stian
2004-06-12 13:45 ` Manuel Arostegui Ramirez
2004-06-12 13:50 ` Kalin KOZHUHAROV [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-12 13:14 stian
2004-06-12 12:26 stian
2004-06-11 12:20 Gard Spreemann
2004-06-11 12:10 stian
2004-06-10 19:27 Bård Kalbakk
2004-06-10 18:59 Lars Age Kamfjord
2004-06-10 19:21 ` Lars Age Kamfjord
2004-06-09 21:02 stian
2004-06-10 21:00 ` Matias Hermanrud Fjeld
2004-06-11 6:08 ` Lars Age Kamfjord
2004-06-12 2:53 ` Rik van Riel
2004-06-12 3:50 ` Rik van Riel
2004-06-12 13:44 ` Sergey Vlasov
2004-06-12 13:57 ` stian
2004-06-12 14:28 ` Sergey Vlasov
2004-06-12 4:35 ` Matt Mackall
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=40CB0A0A.1010104@ThinRope.net \
--to=kalin@thinrope.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox