From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Cyril Roelandt <tipecaml@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
lenb@kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] acpi_system_write_wakeup_device(): fix error check for unsigned variable.
Date: Thu, 22 Nov 2012 23:40:26 +0100 [thread overview]
Message-ID: <27097726.Soe6qubrSj@vostro.rjw.lan> (raw)
In-Reply-To: <1353544495-25277-1-git-send-email-tipecaml@gmail.com>
On Thursday, November 22, 2012 01:34:55 AM Cyril Roelandt wrote:
> The LEN variable is unsigned, therefore checking whether it is less than 0 is
> useless. Also drop the LEN variable, since the COUNT parameter can be used
> instead.
Applied (under a different subject).
Thanks,
Rafael
> Signed-off-by: Cyril Roelandt <tipecaml@gmail.com>
> ---
> drivers/acpi/proc.c | 11 ++++-------
> 1 file changed, 4 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/acpi/proc.c b/drivers/acpi/proc.c
> index 27adb09..ef98796 100644
> --- a/drivers/acpi/proc.c
> +++ b/drivers/acpi/proc.c
> @@ -362,16 +362,13 @@ acpi_system_write_wakeup_device(struct file *file,
> struct list_head *node, *next;
> char strbuf[5];
> char str[5] = "";
> - unsigned int len = count;
>
> - if (len > 4)
> - len = 4;
> - if (len < 0)
> - return -EFAULT;
> + if (count > 4)
> + count = 4;
>
> - if (copy_from_user(strbuf, buffer, len))
> + if (copy_from_user(strbuf, buffer, count))
> return -EFAULT;
> - strbuf[len] = '\0';
> + strbuf[count] = '\0';
> sscanf(strbuf, "%s", str);
>
> mutex_lock(&acpi_device_lock);
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2012-11-22 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 1:54 [PATCH] " Cyril Roelandt
2012-11-21 0:44 ` Rafael J. Wysocki
2012-11-22 0:05 ` Cyril Roelandt
2012-11-22 0:23 ` Rafael J. Wysocki
2012-11-22 0:30 ` Cyril Roelandt
2012-11-22 0:34 ` [PATCH v2] " Cyril Roelandt
2012-11-22 22:40 ` Rafael J. Wysocki [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=27097726.Soe6qubrSj@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=kernel-janitors@vger.kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tipecaml@gmail.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 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®