From: Peter Osterlund <petero2@telia.com>
To: Martin Sarsale <lists@runa.sytes.net>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Jens Axboe <axboe@suse.de>
Subject: Re: segfault when unloading module loop in 2.6.0-test3+ck patches
Date: 17 Aug 2003 22:51:41 +0200 [thread overview]
Message-ID: <m28yps57oi.fsf@p4.localdomain> (raw)
In-Reply-To: <20030817042751.379428cf.lists@runa.sytes.net>
(I'm resending this because I previously had sendmail configuration
problems. Sorry if you receive this message twice.)
Martin Sarsale <lists@runa.sytes.net> writes:
> Dear all: I was playing with the crypto support, and when I tried to
> unload the module "loop" I got a segfault and after that lsmod hung
>
> dmesg says (I'll include the hda lines in case they've something to do):
>
> Unable to handle kernel paging request at virtual address 010000bf
> printing eip:
> c01d5564
> *pde = 00000000
> Oops: 0000 [#1]
> CPU: 0
> EIP: 0060:[<c01d5564>] Not tainted
> EFLAGS: 00210202
> EIP is at kobject_del+0x34/0x80
> eax: 0100007f ebx: d5c9f850 ecx: d5c9f850 edx: 0100007f
> esi: d4f43960 edi: d4f43a24 ebp: 00000880 esp: cf401eec
> ds: 007b es: 007b ss: 0068
> Process rmmod (pid: 27599, threadinfo=cf400000 task=caac72b0)
> Stack: dbfe7ab8 00200282 d654d200 d5c9f850 c01d55c3 d5c9f850 d5c9f800 c023bb8a
> d5c9f850 d5c9f800 c023f5de d5c9f800 d4f43960 c037b018 c0240523 d4f43960
> d4f43960 d4f43960 c017fc0d d4f43960 00000000 00000000 c037b018 00000000
> Call Trace:
> [<c01d55c3>] kobject_unregister+0x13/0x30
> [<c023bb8a>] elv_unregister_queue+0x1a/0x40
> [<c023f5de>] blk_unregister_queue+0x1e/0x60
> [<c0240523>] unlink_gendisk+0x13/0x40
> [<c017fc0d>] del_gendisk+0x6d/0xe0
> [<dcb7a133>] cleanup_module+0x63/0x7e [loop]
> [<c012f6f9>] sys_delete_module+0x119/0x1a0
> [<c01427dc>] do_munmap+0x14c/0x190
> [<c010929b>] syscall_call+0x7/0xb
I have the same problem in 2.6.0-test3-bk5 when I unload the loop
module, even when not using any crypto stuff. The patch below fixes
it:
linux-petero/drivers/block/loop.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
diff -puN drivers/block/loop.c~loop-oops-fix drivers/block/loop.c
--- linux/drivers/block/loop.c~loop-oops-fix 2003-08-17 19:19:22.000000000 +0200
+++ linux-petero/drivers/block/loop.c 2003-08-17 20:33:03.000000000 +0200
@@ -1198,6 +1198,7 @@ int __init loop_init(void)
lo->lo_queue = blk_alloc_queue(GFP_KERNEL);
if (!lo->lo_queue)
goto out_mem4;
+ init_timer(&lo->lo_queue->unplug_timer);
disks[i]->queue = lo->lo_queue;
init_MUTEX(&lo->lo_ctl_mutex);
init_MUTEX_LOCKED(&lo->lo_sem);
@@ -1237,8 +1238,8 @@ void loop_exit(void)
int i;
for (i = 0; i < max_loop; i++) {
- blk_put_queue(loop_dev[i].lo_queue);
del_gendisk(disks[i]);
+ blk_put_queue(loop_dev[i].lo_queue);
put_disk(disks[i]);
}
devfs_remove("loop");
_
--
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340
next prev parent reply other threads:[~2003-08-17 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 7:27 Martin Sarsale
2003-08-17 20:51 ` Peter Osterlund [this message]
2003-08-17 20:59 ` Andrew Morton
2003-08-17 21:15 ` Peter Osterlund
2003-08-17 21:36 ` Andrew Morton
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=m28yps57oi.fsf@p4.localdomain \
--to=petero2@telia.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@runa.sytes.net \
/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®