From: Jens Axboe <axboe@suse.de>
To: Andrzej Krzysztofowicz <ankry@green.mif.pg.gda.pl>
Cc: proski@gnu.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@transmeta.com>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.4-ac4 - oops on unload "cdrom" module
Date: Sat, 5 May 2001 00:19:17 +0200 [thread overview]
Message-ID: <20010505001917.P16507@suse.de> (raw)
In-Reply-To: <200105042110.XAA20705@green.mif.pg.gda.pl>
In-Reply-To: <200105042110.XAA20705@green.mif.pg.gda.pl>; from ankry@green.mif.pg.gda.pl on Fri, May 04, 2001 at 11:10:22PM +0200
On Fri, May 04 2001, Andrzej Krzysztofowicz wrote:
> > This oops happens when I run "rmmod cdrom" on a 2.4.4-ac4 kernel with
> > CONFIG_SYSCTL enabled. It doesn't happen if CONFIG_SYSCTL is disabled.
> >
> > sr_mod isn't loaded at this point. Reference to sd_mod looks weird. After
> > this oops the "cdrom" module remains in memory in the "deleted" state.
>
> > Unable to handle kernel NULL pointer dereference at virtual address 00000008
> [...]
> > >>EIP; c0118051 <unregister_sysctl_table+5/2c> <=====
>
> The following patch fixes unloading of cdrom module when no cdrom driver
> loaded (2.4.5-pre, 2.4.4-ac):
>
> --- drivers/cdrom/cdrom.c.old Fri May 4 22:44:31 2001
> +++ drivers/cdrom/cdrom.c Fri May 4 22:54:36 2001
> @@ -2698,7 +2698,8 @@
>
> static void cdrom_sysctl_unregister(void)
> {
> - unregister_sysctl_table(cdrom_sysctl_header);
> + if (cdrom_sysctl_header)
> + unregister_sysctl_table(cdrom_sysctl_header);
> }
>
> #endif /* CONFIG_SYSCTL */
Thanks applied.
--
Jens Axboe
next prev parent reply other threads:[~2001-05-04 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 21:10 2.4.4-ac4 - oops on unload "cdrom" module Andrzej Krzysztofowicz
2001-05-04 22:02 ` Pavel Roskin
2001-05-04 22:21 ` Jens Axboe
2001-05-04 22:19 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-04 16:23 Pavel Roskin
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=20010505001917.P16507@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ankry@green.mif.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.org \
--cc=torvalds@transmeta.com \
/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.