From: Andrew Morton <akpm@linux-foundation.org>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] ACPI: fix oops after dock driver fails to initialize
Date: Wed, 9 May 2007 17:42:03 -0700 [thread overview]
Message-ID: <20070509174203.93b5b02f.akpm@linux-foundation.org> (raw)
In-Reply-To: <4640FC3B.3010005@redhat.com>
On Tue, 08 May 2007 18:39:55 -0400
Chuck Ebbert <cebbert@redhat.com> wrote:
>
You didn't write much.
Oh, it was an attachment. thwap.
> ACPI: fix oops after dock driver fails to initialize
>
> The driver tests the dock_station pointer for nonnull
> to check whether it has initialized properly. But in
> some cases dock_station will be non-null after being
> freed when driver init fails. Fix by zeroing the
> pointer after freeing.
>
> Signed-off-by: Chuck Ebbert <cebbert@redhat.com>
>
> ---
> drivers/acpi/dock.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> --- 2.6.21-d390.orig/drivers/acpi/dock.c
> +++ 2.6.21-d390/drivers/acpi/dock.c
> @@ -698,6 +698,7 @@ static int dock_add(acpi_handle handle)
> if (ret) {
> printk(KERN_ERR PREFIX "Error %d registering dock device\n", ret);
> kfree(dock_station);
> + dock_station = NULL;
> return ret;
> }
> ret = device_create_file(&dock_device.dev, &dev_attr_docked);
> @@ -705,6 +706,7 @@ static int dock_add(acpi_handle handle)
> printk("Error %d adding sysfs file\n", ret);
> platform_device_unregister(&dock_device);
> kfree(dock_station);
> + dock_station = NULL;
> return ret;
> }
> ret = device_create_file(&dock_device.dev, &dev_attr_undock);
> @@ -713,6 +715,7 @@ static int dock_add(acpi_handle handle)
> device_remove_file(&dock_device.dev, &dev_attr_docked);
> platform_device_unregister(&dock_device);
> kfree(dock_station);
> + dock_station = NULL;
> return ret;
> }
>
> @@ -725,6 +728,7 @@ static int dock_add(acpi_handle handle)
> dd = alloc_dock_dependent_device(handle);
> if (!dd) {
> kfree(dock_station);
> + dock_station = NULL;
> ret = -ENOMEM;
> goto dock_add_err_unregister;
> }
> @@ -752,6 +756,7 @@ dock_add_err_unregister:
> device_remove_file(&dock_device.dev, &dev_attr_undock);
> platform_device_unregister(&dock_device);
> kfree(dock_station);
> + dock_station = NULL;
> return ret;
> }
>
> @@ -785,6 +790,7 @@ static int dock_remove(void)
>
> /* free dock station memory */
> kfree(dock_station);
> + dock_station = NULL;
> return 0;
> }
>
I think you're missing a case, here:
ret = device_create_file(&dock_device.dev, &dev_attr_uid);
if (ret) {
printk("Error %d adding sysfs file\n", ret);
platform_device_unregister(&dock_device);
kfree(dock_station);
return ret;
}
also, the code duplication in there is unpleasing. Doesn't this look
better?
drivers/acpi/dock.c | 26 ++++++++++++--------------
1 files changed, 12 insertions(+), 14 deletions(-)
diff -puN drivers/acpi/dock.c~acpi-fix-oops-after-dock-driver-fails-to-initialize drivers/acpi/dock.c
--- a/drivers/acpi/dock.c~acpi-fix-oops-after-dock-driver-fails-to-initialize
+++ a/drivers/acpi/dock.c
@@ -714,31 +714,24 @@ static int dock_add(acpi_handle handle)
dock_device.name = dock_device_name;
ret = platform_device_register(&dock_device);
if (ret) {
- printk(KERN_ERR PREFIX "Error %d registering dock device\n", ret);
- kfree(dock_station);
- return ret;
+ printk(KERN_ERR PREFIX "Error %d registering dock device\n",
+ ret);
+ goto err;
}
ret = device_create_file(&dock_device.dev, &dev_attr_docked);
if (ret) {
printk("Error %d adding sysfs file\n", ret);
- platform_device_unregister(&dock_device);
- kfree(dock_station);
- return ret;
+ goto err_register;
}
ret = device_create_file(&dock_device.dev, &dev_attr_undock);
if (ret) {
printk("Error %d adding sysfs file\n", ret);
- device_remove_file(&dock_device.dev, &dev_attr_docked);
- platform_device_unregister(&dock_device);
- kfree(dock_station);
- return ret;
+ goto err_sysfs_1;
}
ret = device_create_file(&dock_device.dev, &dev_attr_uid);
if (ret) {
printk("Error %d adding sysfs file\n", ret);
- platform_device_unregister(&dock_device);
- kfree(dock_station);
- return ret;
+ goto err_sysfs_2;
}
/* Find dependent devices */
@@ -749,7 +742,6 @@ static int dock_add(acpi_handle handle)
/* add the dock station as a device dependent on itself */
dd = alloc_dock_dependent_device(handle);
if (!dd) {
- kfree(dock_station);
ret = -ENOMEM;
goto dock_add_err_unregister;
}
@@ -773,10 +765,15 @@ static int dock_add(acpi_handle handle)
dock_add_err:
kfree(dd);
dock_add_err_unregister:
+err_sysfs_2:
device_remove_file(&dock_device.dev, &dev_attr_docked);
+err_sysfs_1:
device_remove_file(&dock_device.dev, &dev_attr_undock);
+err_register:
platform_device_unregister(&dock_device);
+err:
kfree(dock_station);
+ dock_station = NULL;
return ret;
}
@@ -810,6 +807,7 @@ static int dock_remove(void)
/* free dock station memory */
kfree(dock_station);
+ dock_station = NULL;
return 0;
}
_
prev parent reply other threads:[~2007-05-10 0:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 22:39 [patch] ACPI: fix oops after dock driver fails to initialize Chuck Ebbert
2007-05-10 0:42 ` Andrew Morton [this message]
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=20070509174203.93b5b02f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cebbert@redhat.com \
--cc=kristen.c.accardi@intel.com \
--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.