mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Connolly <slarti@netsoc.dkit.ie>
To: Manuel Arostegui Ramirez <manuel@todo-linux.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: new kernel bug
Date: Sat, 12 Jun 2004 14:37:34 +0100	[thread overview]
Message-ID: <200406121437.44155.slarti@netsoc.dkit.ie> (raw)
In-Reply-To: <200406121442.48691.manuel@todo-linux.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 12 June 2004 13:42, Manuel wrote:
> I'm thinking about download patch-2.6.7-rc3, maybe it will fixed that bug.
> Any ideas?

I use 2.6.7-rc2-mm2, and the crash.c program produces the console race,
2.6.7-rc3 maybe not worth the effort mate.

How would I go about trapping SIGFPE to prevent end users of login server 
crashing the box, can anyone point me in the direction of advice? We really 
don't want to have to disable user logins! 

Thanks,
- -David Connolly
admin2 on netsoc-dkit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAywcjHyDWKYgIFNcRAkcKAJ9rrp7s2h5HZhVP9/7OpMtGzljgAACfaEIx
Ph+ubI+G3sJPC80AYhDqVnw=
=0EFM
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-06-12 13:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-12  9:59 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 [this message]
2004-06-12 15:08     ` Han Boetes
2004-06-12 15:08       ` Manuel Arostegui Ramirez
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
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=200406121437.44155.slarti@netsoc.dkit.ie \
    --to=slarti@netsoc.dkit.ie \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manuel@todo-linux.com \
    /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

all inboxes | Powered by JetHome®