From: Matt <matt@progsoc.uts.edu.au>
To: Andrew Morton <akpm@zip.com.au>
Cc: Berend De Schouwer <bds@jhb.ucs.co.za>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Kernel Oops on cat /proc/ioports
Date: Wed, 12 Dec 2001 13:57:13 +1100 [thread overview]
Message-ID: <20011212135713.M5809@ftoomsh.progsoc.uts.edu.au> (raw)
In-Reply-To: <1008073796.5535.5.camel@bds.ucs.co.za> <3C16ADB1.F9E847E9@zip.com.au>
In-Reply-To: <3C16ADB1.F9E847E9@zip.com.au>; from akpm@zip.com.au on Tue, Dec 11, 2001 at 05:06:57PM -0800
On Tue, Dec 11, 2001 at 05:06:57PM -0800, Andrew Morton wrote:
> Berend De Schouwer wrote:
>> [1.] One line summary of the problem:
>> Running "cat /proc/ioports" causes a segfault and kernel oops.
>> ...
>> [7.3.] Module information (from /proc/modules):
>> cyclades 147616 16 (autoclean)
> cyclades does request_region(), but forgets to do release_region().
> This will leave the region allocated in kernel data structures, but
> its "name" field resides in module memory.
> So if you load cyclades.o, then rmmod it, then cat /proc/ioports,
> you'll touch unmapped memory and go boom.
> Some brave soul needs to teach cyclades about release_region().
> Shame the Nobel prizes are all gone this year.
speaking of living in module memory, a similar thing happens with the
via-rhine driver. after my machine has been up for a few hours the
"via-rhine" string in /proc/iomem and /proc/ioports gets over written
and prints garbage. since this has never been the cause for an oops on
my machine i never bothered reporting it. if anyone wants details i'll
provide.
matt
next prev parent reply other threads:[~2001-12-12 2:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 12:29 Berend De Schouwer
2001-12-12 0:22 ` Randy.Dunlap
2001-12-12 0:31 ` {multiple} " Randy.Dunlap
2001-12-12 1:06 ` PROBLEM: " Andrew Morton
2001-12-12 2:57 ` Matt [this message]
2001-12-12 3:10 ` Andrew Morton
2001-12-12 3:25 ` Matt
2001-12-12 1:25 ` Andrew Morton
2001-12-12 10:30 ` Berend De Schouwer
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=20011212135713.M5809@ftoomsh.progsoc.uts.edu.au \
--to=matt@progsoc.uts.edu.au \
--cc=akpm@zip.com.au \
--cc=bds@jhb.ucs.co.za \
--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
all inboxes | Powered by JetHome®