All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Loschwitz <madkiss@madkiss.org>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: local DDOS? Kernel panic when accessing /proc/ioports
Date: Fri, 5 Aug 2005 23:49:54 +0200	[thread overview]
Message-ID: <20050805214954.GA25533@minerva.local.lan> (raw)
In-Reply-To: <Pine.LNX.4.61.0508051538390.6245@chaos.analogic.com>

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

On Fri, Aug 05, 2005 at 03:40:26PM -0400, linux-os (Dick Johnson) wrote:
> 
> On Fri, 5 Aug 2005, Martin Loschwitz wrote:
> 
> > Hi folks,
> >
> > 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?
> >
> > Ooops and ksymoops-output is attached.
> >
> 
> This can happen if a module is unloaded that doesn't free its
> resources! Been there, done that.
> 

"This can happen" is not an acceptable explanation, I think. Modules should
not be able to kill the kernel -- apart from that, I can trigger the bug in
the very early "ash-system" that KNOPPIX provides. At that time, the modules
listed below were the only ones loaded -- no others, and I am also sure that
until that point, no modules were unloaded.

sbp2 ohci1394 usb_storage ub ehci_hcd usbcore

-- 
  .''`.   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:50 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 [this message]
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
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=20050805214954.GA25533@minerva.local.lan \
    --to=madkiss@madkiss.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.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 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.