public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, greg@kroah.com
Subject: Re: 2.6.3rc4 ali1535 i2c driver rmmod oops.
Date: Wed, 18 Feb 2004 03:49:25 +0000	[thread overview]
Message-ID: <20040218034925.GI6242@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0402171941580.2686@home.osdl.org>

On Tue, Feb 17, 2004 at 07:47:01PM -0800, Linus Torvalds wrote:
 > 
 > 
 > On Wed, 18 Feb 2004, Dave Jones wrote:
 > >
 > > Erk, whats going on here ?
 > 
 > Normally this would mean that somebody is trying to "kfree" a pointer that 
 > wasn't allocated with "kmalloc()". That seems unlikely in this case, so it 
 > might be a double free or some other internal corruption..
 > 
 > That "sys_delete_module()" thing seems like some stale kernel stack 
 > contents, so it's possible that that is the thing that messed up and left 
 > something in an inconsistent state.
 > 
 > Do you know what module it was?

I felt masochistic, so decided to 'see what would happen' when I ran this..

for i in `find /lib/modules/2.6.2-prep/ -name *.ko`
do
	MOD=`basename $i | sed s/.ko//`
	echo module: $i
	echo inserting
	/sbin/modprobe $MOD
	sync
	echo removing
	/sbin/rmmod $MOD
	echo
	sync
	#sleep 1
done

.. And then sat back and watched the carnage.

After the ali1535 i2c module blew up and took the box with it,
I rebooted, and did a modprobe / rmmod of that module alone.
Exactly the same result. Reproducable every time.

		Dave


  reply	other threads:[~2004-02-18  3:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18  3:15 2.6.3rc4 ali1535 i2c driver rmmod oops Dave Jones
2004-02-18  3:47 ` Linus Torvalds
2004-02-18  3:49   ` Dave Jones [this message]
2004-02-18  4:00     ` Linus Torvalds
2004-02-18  4:02       ` Dave Jones
2004-02-18  4:34         ` viro
2004-02-18  4:01 ` Greg KH
2004-02-18  4:17   ` Dave Jones
2004-02-21  7:19   ` Jean Delvare
2004-02-24  0:27     ` Greg KH

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=20040218034925.GI6242@redhat.com \
    --to=davej@redhat.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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