From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@osdl.org>, linux-scsi@vger.kernel.org
Subject: [PATCH] Re: Oops on megaraid.
Date: Wed, 5 Jan 2005 18:04:57 +0000 [thread overview]
Message-ID: <20050105180457.GK26051@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20050105174752.GA6859@animx.eu.org>
On Wed, Jan 05, 2005 at 12:47:52PM -0500, Wakko Warner wrote:
> Kernel: 2.6.8.1 vanilla
> Card: Dell PERC DC/2 (megaraid)
>
> The oops happened when I attempted to unload the megaraid module. Before
> doing this, I ran the dellmgr program to reconfigure the raid.
>
> Before the "oops" text, I saw:
> Badness in remove_proc_entry at fs/proc/generic.c:688
> [<c017c3fa>] remove_proc_entry+0x10a/0x150
> [<d88f6e3e>] megaraid_exit+0x2e/0x3e [megaraid]
> [<c012c690>] sys_delete_module+0x150/0x1a0
> [<c0142a00>] do_munmap+0x140/0x190
> [<c010513b>] syscall_call+0x7/0xb
Someone's removing non-empty directory in procfs. Let's see...
Indeed.
#ifdef CONFIG_PROC_FS
remove_proc_entry("megaraid", &proc_root);
#endif
pci_unregister_driver(&megaraid_pci_driver);
so we remove /proc/megaraid and then procees to remove controllers found
by driver. Each of those has a subdirectory in /proc/megaraid...
Fix is trivial:
diff -urN RC10-bk6-base/drivers/scsi/megaraid.c RC10-bk6-current/drivers/scsi/megaraid.c
--- RC10-bk6-base/drivers/scsi/megaraid.c 2004-12-25 01:04:29.000000000 -0500
+++ RC10-bk6-current/drivers/scsi/megaraid.c 2005-01-05 13:03:51.609698587 -0500
@@ -5109,11 +5109,11 @@
*/
unregister_chrdev(major, "megadev");
+ pci_unregister_driver(&megaraid_pci_driver);
+
#ifdef CONFIG_PROC_FS
remove_proc_entry("megaraid", &proc_root);
#endif
-
- pci_unregister_driver(&megaraid_pci_driver);
}
module_init(megaraid_init);
next prev parent reply other threads:[~2005-01-05 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 17:47 Wakko Warner
2005-01-05 18:04 ` Al Viro [this message]
2005-01-05 22:33 ` [PATCH] " Wakko Warner
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=20050105180457.GK26051@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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
all inboxes | Powered by JetHome®