From: Manuel Arostegui Ramirez <manuel@todo-linux.com>
To: Gianni Tedesco <gianni@scaramanga.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Local DoS attack on i386 (was: new kernel bug)
Date: Mon, 14 Jun 2004 16:08:16 +0200 [thread overview]
Message-ID: <200406141608.16319.manuel@todo-linux.com> (raw)
In-Reply-To: <1087221517.3375.3.camel@sherbert>
El Lunes 14 Junio 2004 15:58, Gianni Tedesco escribió:
> On Sat, 2004-06-12 at 11:59 +0200, Manuel Arostegui Ramirez wrote:
> > Somebody know a patch to solved this new bug?
> > http://reviewed.homelinux.org/news/2004-06-11_kernel_crash/index.html.en
> > Affected versions:
> > * Linux 2.6.x
> > o Linux 2.6.7-rc2
> > o Linux 2.6.6 (all versions)
> > o Linux 2.6.6 SMP (verified by riven)
> > o Linux 2.6.5-gentoo (verified by RatiX)
> > o Linux 2.6.5-mm6 - (verified by Mariux)
> > * Linux 2.4.2x
> > o Linux 2.4.26 vanilla
> > o Linux 2.4.26-rc1 vanilla
> > o Linux 2.4.26-gentoo-r1
> > o Linux 2.4.22
>
> Seems to be a scheduler race or something?
The timer and fpu stuff locks the console race, io-schedules also stops.
This seems serious.
Look at the original thread, it's called:
"timer + fpu stuff locks my console race"
Here you are:
http://marc.theaimsgroup.com/?l=linux-kernel&m=108704334308688&w=2
Cheers
--
Manuel Arostegui Ramirez #Linux Registered User 200896
next prev parent reply other threads:[~2004-06-14 14:09 UTC|newest]
Thread overview: 12+ 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
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 [this message]
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
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=200406141608.16319.manuel@todo-linux.com \
--to=manuel@todo-linux.com \
--cc=gianni@scaramanga.co.uk \
--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