public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Loschwitz <madkiss@madkiss.org>
To: Chris Wright <chrisw@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: local DDOS? Kernel panic when accessing /proc/ioports
Date: Fri, 5 Aug 2005 23:52:47 +0200	[thread overview]
Message-ID: <20050805215247.GA25652@minerva.local.lan> (raw)
In-Reply-To: <20050805195056.GB7991@shell0.pdx.osdl.net>

[-- Attachment #1: Type: text/plain, Size: 1394 bytes --]

On Fri, Aug 05, 2005 at 12:50:56PM -0700, Chris Wright wrote:
> * Martin Loschwitz (madkiss@madkiss.org) wrote:
> > I just ran into the following problem: Having updated my box to 2.6.12.3, 
> > I tried to start YaST2 and noticed a kernel panic (see below). Some quick
> > debugging brought the result that the kernel crashes while some user (not
> > even root ...) tries to access /proc/ioports. Is this a known problem and
> > if so, is a fix available?
> 
> First I've heard of it.  I can't trigger here with simple cat
> /proc/ioports.  Must be specific to your setup.  What was the last
> working kernel, and what's that ioport output look like?
> 

The situation in this case is somewhat obscene ... Originally, I had exactly
this problem while using the Knoppix standard kernel (2.6.11 vanilla SMP). I
then went to compile 2.6.12.3, also with SMP, and it showed exactly the same
problem. I disable SMP, tried again -- voila, it worked.

The kernel that I am encountering this error again now is 2.6.12.3 -- without
SMP or whatsoever. I'm just out of ideas on how to fix it this time.

> thanks,
> -chris

-- 
  .''`.   Martin Loschwitz           Debian GNU/Linux developer
 : :'  :  madkiss@madkiss.org        madkiss@debian.org
 `. `'`   http://www.madkiss.org/    people.debian.org/~madkiss/
   `-     Use Debian GNU/Linux 3.0!  See http://www.debian.org/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-05 21:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05 19:26 local DDOS? Kernel panic when accessing /proc/ioports Martin Loschwitz
2005-08-05 19:40 ` linux-os (Dick Johnson)
2005-08-05 21:49   ` Martin Loschwitz
2005-08-05 22:33     ` Andrew Morton
2005-08-05 22:42       ` Martin Loschwitz
2005-08-08  6:53     ` Jan Engelhardt
2005-08-08 11:19     ` linux-os (Dick Johnson)
2005-08-05 19:50 ` Chris Wright
2005-08-05 21:52   ` Martin Loschwitz [this message]
2005-08-05 23:29     ` Marc Ballarin
2005-08-05 23:43       ` Martin Loschwitz
2005-08-05 20:03 ` Lee Revell
2005-08-05 21:53   ` Martin Loschwitz

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=20050805215247.GA25652@minerva.local.lan \
    --to=madkiss@madkiss.org \
    --cc=chrisw@osdl.org \
    --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