From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: hzy@cs.otago.ac.nz
Cc: zhiyi6@xtra.co.nz, penberg@cs.helsinki.fi, hnagar2@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: Slab corruption after unloading a module
Date: Sat, 15 Apr 2006 21:21:47 -0700 [thread overview]
Message-ID: <20060415212147.6e9b0c11.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060412230439.WMCC8268.mta4-rme.xtra.co.nz@[202.27.184.228]>
On Thu, 13 Apr 2006 11:04:39 +1200 Zhiyi Huang wrote:
> > 2.6.8 is an old kernel, you could very well be hitting a kernel bug
> > that has been fixed already. Can you reproduce this with 2.6.16?
>
> I will try that soon.
>
> > Also,
> > you're not including sources to your module so it's impossible to tell
> > whether you're doing something wrong.
> >
> > Pekka
>
> Below is my baby module which only uses kmalloc and kfree for my device
> structure. I found the slab corruption address is the address of the structure.
> It seems to be a bug for kmalloc and kfree.
> /* The parameter for testing */
> int major=0;
> MODULE_PARM(major, "i");
> MODULE_PARM_DESC(major, "device major number");
Hi,
I had no problem loading and unloading your module on
2.6.17-rc1 [after changing MODULE_PARM() to
module_param(major, int, 0644);
].
---
~Randy
next prev parent reply other threads:[~2006-04-16 4:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 23:04 Zhiyi Huang
2006-04-12 23:30 ` Randy.Dunlap
2006-04-16 4:21 ` Randy.Dunlap [this message]
2006-04-16 9:38 ` zhiyi huang
2006-04-17 2:17 ` Randy.Dunlap
2006-04-17 2:55 ` Randy.Dunlap
2006-04-17 21:49 ` zhiyi huang
2006-04-18 5:01 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2006-04-16 10:43 Andrey Borzenkov
2006-04-17 22:08 ` zhiyi huang
2006-04-17 22:09 ` Arjan van de Ven
2006-04-17 22:23 ` zhiyi huang
2006-04-12 0:37 Zhiyi Huang
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=20060415212147.6e9b0c11.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=hnagar2@gmail.com \
--cc=hzy@cs.otago.ac.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=zhiyi6@xtra.co.nz \
/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®