From: Xiong Jiang <jxiong@offtopic.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug] module unloading or unmap_vma bug ?
Date: Tue, 11 Mar 2003 21:08:50 -0500 [thread overview]
Message-ID: <20030312020849.GA8228@offtopic.org> (raw)
Hi, folks,
Maybe this was reported or maybe not...
Plain 2.5.64 kernel, with isofs as modules, using the new module-init-tool.
Try modprobe isofs and unload it, then try it again, then I got following
segfault. Then modules system got something wrong and have to reboot.
And shutdown procedure is halted when iptable service is to be stopped.
Here is now to reproduce it:
/sbin/modprobe isofs
/sbin/rmmod isofs
/sbin/rmmod zlib_inflate
/sbin/modprobe isofs
/sbin/rmmod isofs
Process rmmod (pid: 693, threadinfo=cd096000 task=cd2d07c0)
Stack: 40017000 cd097f38 c0141bf4 c03035a4 d0864d74 d0864d60 00000000 cd097f2c
c01aba94 d0864d74 d0864d74 cd097f3c c01abab4 d0864d74 00000000 cd097f50
c016a562 d0864d74 c0288518 d0864f40 cd097f5c d0861ac2 d0864d60 cd097fbc
Call Trace:
[<c0141bf4>] unmap_vmas+0xc4/0x220
[<d0864d74>] iso9660_fs_type+0x14/0x80 [isofs]
[<d0864d60>] iso9660_fs_type+0x0/0x80 [isofs]
[<c01aba94>] kobject_del+0x14/0x20
[<d0864d74>] iso9660_fs_type+0x14/0x80 [isofs]
[<d0864d74>] iso9660_fs_type+0x14/0x80 [isofs]
[<c01abab4>] kobject_unregister+0x14/0x20
[<d0864d74>] iso9660_fs_type+0x14/0x80 [isofs]
[<c016a562>] unregister_filesystem+0x32/0x40
[<d0864d74>] iso9660_fs_type+0x14/0x80 [isofs]
[<d0864f40>] +0x0/0x140 [isofs]
[<d0861ac2>] +0x12/0x20 [isofs]
[<d0864d60>] iso9660_fs_type+0x0/0x80 [isofs]
[<c01330d3>] sys_delete_module+0x1b3/0x1f0
[<c0145667>] sys_munmap+0x57/0x80
[<c010b282>] sysenter_entry+0x52/0x70
Code: 0f 0b 0a 01 56 1e 26 c0 ff 07 83 4f 04 08 85 ff 0f 84 37 01
reply other threads:[~2003-03-12 1:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030312020849.GA8228@offtopic.org \
--to=jxiong@offtopic.org \
--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 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.