From: Len Brown <lenb@kernel.org>
To: Dmitry Torokhov <dtor@insightbb.com>
Cc: linux-acpi@vger.kernel.org,
Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Subject: Re: [PATCH] Fix potential oops in dock driver
Date: Wed, 18 Jul 2007 20:38:22 -0400 [thread overview]
Message-ID: <200707182038.23028.lenb@kernel.org> (raw)
In-Reply-To: <200707180110.24792.dtor@insightbb.com>
Applied.
thanks,
-Len
On Wednesday 18 July 2007 01:10, Dmitry Torokhov wrote:
> [PATCH] Fix potential oops in dock driver
> From:
> Dmitry Torokhov <dtor@insightbb.com>
> To:
> linux-acpi@vger.kernel.org
> CC:
> Kristen Carlson Accardi <kristen.c.accardi@intel.com>, Len Brown <len.brown@intel.com>
> Date:
> Today 01:10:24 am
>
> Spam Status: Spamassassin 0% probability of being spam.
>
> Full report:
> No, score=-2.1 required=5.0 tests=AWL,BAYES_00,FORGED_RCVD_HELO autolearn=ham version=3.1.9
> Possible needed for -stable as well.
>
> --
> Dmitry
>
> ACPI: dock - fix an oops when _DCK evaluation fails
>
> Data returned by acpi_get_name in acpi_buffer is not acpi_object and
> therefore should not be cast to it, otherwise we'll get an nice oops
> trying to print error message.
>
> Also print name of the ACPI object corresponding to the docking station
> and elevate severity of the message printed when _DCK fails to KERN_ERR.
>
> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
> ---
> drivers/acpi/dock.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> Index: linux/drivers/acpi/dock.c
> ===================================================================
> --- linux.orig/drivers/acpi/dock.c
> +++ linux/drivers/acpi/dock.c
> @@ -380,12 +380,11 @@ static void handle_dock(struct dock_stat
> union acpi_object arg;
> struct acpi_buffer buffer = { ACPI_ALLOCATE_BUFFER, NULL };
> struct acpi_buffer name_buffer = { ACPI_ALLOCATE_BUFFER, NULL };
> - union acpi_object *obj;
>
> acpi_get_name(ds->handle, ACPI_FULL_PATHNAME, &name_buffer);
> - obj = name_buffer.pointer;
>
> - printk(KERN_INFO PREFIX "%s\n", dock ? "docking" : "undocking");
> + printk(KERN_INFO PREFIX "%s - %s\n",
> + (char *)name_buffer.pointer, dock ? "docking" : "undocking");
>
> /* _DCK method has one argument */
> arg_list.count = 1;
> @@ -394,7 +393,8 @@ static void handle_dock(struct dock_stat
> arg.integer.value = dock;
> status = acpi_evaluate_object(ds->handle, "_DCK", &arg_list, &buffer);
> if (ACPI_FAILURE(status))
> - pr_debug("%s: failed to execute _DCK\n", obj->string.pointer);
> + printk(KERN_ERR PREFIX "%s - failed to execute _DCK\n",
> + (char *)name_buffer.pointer);
> kfree(buffer.pointer);
> kfree(name_buffer.pointer);
> }
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2007-07-19 0:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 5:10 [PATCH] Fix potential oops in dock driver Dmitry Torokhov
2007-07-19 0:38 ` Len Brown [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=200707182038.23028.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=dtor@insightbb.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-acpi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox