From: khali@linux-fr.org (Jean Delvare)
To: Greg KH <greg@kroah.com>
Cc: davej@redhat.com, linux-kernel@vger.kernel.org,
sensors@Stimpy.netroedge.com
Subject: 2.6.3rc4 ali1535 i2c driver rmmod oops.
Date: Thu, 19 May 2005 06:24:42 +0000 [thread overview]
Message-ID: <20040221081953.60fe4165.khali@linux-fr.org> (raw)
In-Reply-To: <20040218040153.GB6729@kroah.com>
> Oh nevermind, that's just a dumb driver. It's doing a release_region
> on memory it didn't get. Stupid, stupid, stupid...
While we're at it, what about fixing two other drivers that obviously
have the same problem?
(BTW I didn't get an oops as I tried reproducing the problem, only a
"Trying to free nonexistent resource" in dmesg.)
I'm backporting these fixes to the lm_sensors2 CVS repository at the
moment, thanks for pointing them out.
--- linux-2.6.3/drivers/i2c/busses/i2c-i801.c.orig Thu Feb 5 22:24:55 2004
+++ linux-2.6.3/drivers/i2c/busses/i2c-i801.c Sat Feb 21 08:03:28 2004
@@ -608,6 +608,7 @@
static void __devexit i801_remove(struct pci_dev *dev)
{
i2c_del_adapter(&i801_adapter);
+ release_region(i801_smba, (isich4 ? 16 : 8));
}
static struct pci_driver i801_driver = {
@@ -625,7 +626,6 @@
static void __exit i2c_i801_exit(void)
{
pci_unregister_driver(&i801_driver);
- release_region(i801_smba, (isich4 ? 16 : 8));
}
MODULE_AUTHOR ("Frodo Looijaard <frodol@dds.nl>, "
--- linux-2.6.3/drivers/i2c/busses/i2c-sis5595.c.orig Thu Feb 5 22:24:55 2004
+++ linux-2.6.3/drivers/i2c/busses/i2c-sis5595.c Sat Feb 21 08:03:11 2004
@@ -391,6 +391,7 @@
static void __devexit sis5595_remove(struct pci_dev *dev)
{
i2c_del_adapter(&sis5595_adapter);
+ release_region(sis5595_base + SMB_INDEX, 2);
}
static struct pci_driver sis5595_driver = {
@@ -408,7 +409,6 @@
static void __exit i2c_sis5595_exit(void)
{
pci_unregister_driver(&sis5595_driver);
- release_region(sis5595_base + SMB_INDEX, 2);
}
MODULE_AUTHOR("Frodo Looijaard <frodol@dds.nl>");
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <khali@linux-fr.org>
To: Greg KH <greg@kroah.com>
Cc: davej@redhat.com, linux-kernel@vger.kernel.org,
sensors@Stimpy.netroedge.com
Subject: Re: 2.6.3rc4 ali1535 i2c driver rmmod oops.
Date: Sat, 21 Feb 2004 08:19:53 +0100 [thread overview]
Message-ID: <20040221081953.60fe4165.khali@linux-fr.org> (raw)
In-Reply-To: <20040218040153.GB6729@kroah.com>
> Oh nevermind, that's just a dumb driver. It's doing a release_region
> on memory it didn't get. Stupid, stupid, stupid...
While we're at it, what about fixing two other drivers that obviously
have the same problem?
(BTW I didn't get an oops as I tried reproducing the problem, only a
"Trying to free nonexistent resource" in dmesg.)
I'm backporting these fixes to the lm_sensors2 CVS repository at the
moment, thanks for pointing them out.
--- linux-2.6.3/drivers/i2c/busses/i2c-i801.c.orig Thu Feb 5 22:24:55 2004
+++ linux-2.6.3/drivers/i2c/busses/i2c-i801.c Sat Feb 21 08:03:28 2004
@@ -608,6 +608,7 @@
static void __devexit i801_remove(struct pci_dev *dev)
{
i2c_del_adapter(&i801_adapter);
+ release_region(i801_smba, (isich4 ? 16 : 8));
}
static struct pci_driver i801_driver = {
@@ -625,7 +626,6 @@
static void __exit i2c_i801_exit(void)
{
pci_unregister_driver(&i801_driver);
- release_region(i801_smba, (isich4 ? 16 : 8));
}
MODULE_AUTHOR ("Frodo Looijaard <frodol@dds.nl>, "
--- linux-2.6.3/drivers/i2c/busses/i2c-sis5595.c.orig Thu Feb 5 22:24:55 2004
+++ linux-2.6.3/drivers/i2c/busses/i2c-sis5595.c Sat Feb 21 08:03:11 2004
@@ -391,6 +391,7 @@
static void __devexit sis5595_remove(struct pci_dev *dev)
{
i2c_del_adapter(&sis5595_adapter);
+ release_region(sis5595_base + SMB_INDEX, 2);
}
static struct pci_driver sis5595_driver = {
@@ -408,7 +409,6 @@
static void __exit i2c_sis5595_exit(void)
{
pci_unregister_driver(&sis5595_driver);
- release_region(sis5595_base + SMB_INDEX, 2);
}
MODULE_AUTHOR("Frodo Looijaard <frodol@dds.nl>");
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 3:15 2.6.3rc4 ali1535 i2c driver rmmod oops Dave Jones
2004-02-18 3:47 ` Linus Torvalds
2004-02-18 3:49 ` Dave Jones
2004-02-18 4:00 ` Linus Torvalds
2004-02-18 4:02 ` Dave Jones
2004-02-18 4:34 ` viro
2004-02-18 4:01 ` Greg KH
2005-05-19 6:24 ` Greg KH
2004-02-18 4:17 ` Dave Jones
2005-05-19 6:24 ` Dave Jones
2004-02-21 7:19 ` Jean Delvare [this message]
2005-05-19 6:24 ` Jean Delvare
2004-02-24 0:27 ` Greg KH
2005-05-19 6:24 ` Greg KH
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=20040221081953.60fe4165.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=davej@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@Stimpy.netroedge.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.