From: Keith Owens <kaos@ocs.com.au>
To: Matthew Rench <lists@pelennor.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem rmmod'ing module
Date: Wed, 18 Feb 2004 15:06:21 +1100 [thread overview]
Message-ID: <7711.1077077181@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 17 Feb 2004 15:38:58 MDT." <20040217153858.A11859@pelennor.net>
On Tue, 17 Feb 2004 15:38:58 -0600,
Matthew Rench <lists@pelennor.net> wrote:
>I'm getting some strange behavior while trying to rmmod a module from my
>2.4.21 kernel. Each call to "rmmod" segfaults, leaving the module usage count
>incremented.
kernel/module.c bumps the use count at the start of each query, to
prevent the module being removed while it is being queried. The use
count is droped at the end of normal query processing, but
kernel/module.c is breaking and leaving the raised use count.
>When I strace rmmod, the last few lines are:
>
> query_module(NULL, QM_MODULES, { /* 5 entries */ }, 5) = 0
> query_module("serial", QM_INFO, {address=0xd8816000, size=43620, flags=MOD_RUNNING, usecount=14}, 16) = 0
> query_module( <unfinished ...>
> +++ killed by SIGSEGV +++
Information about the second module in the chain (after "serial") is
corrupt. What does lsmod report?
You should have several oops reports in your syslog. Run the first two
through ksymoops and send in the ksymoops output.
next prev parent reply other threads:[~2004-02-18 4:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 21:38 Matthew Rench
2004-02-18 4:06 ` Keith Owens [this message]
2004-02-18 18:58 ` Matthew Rench
2004-02-19 13:13 ` Keith Owens
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=7711.1077077181@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@pelennor.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®