From: mark gross <markgross@thegnar.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-pm@lists.linux-foundation.org,
Dan Carpenter <error27@gmail.com>,
mark gross <markgross@thegnar.org>
Subject: Re: [PATCH] PM QoS: Allow parsing of ASCII values
Date: Sun, 6 Mar 2011 06:07:14 -0800 [thread overview]
Message-ID: <20110306140714.GA2438@gvim.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1102241154540.2084-100000@iolanthe.rowland.org>
On Thu, Feb 24, 2011 at 12:00:35PM -0500, Alan Stern wrote:
> On Thu, 24 Feb 2011, mark gross wrote:
>
> > > How careful do you want to be here? For example, which of the
> > > following inputs do you want to accept?
> > >
> > > 0x1234
> > > abcd1234
> > > abcd123456
> > > abcd123456\n
> > > abcd1234567
> > > 1234567890
> > > 1234567890\n
> > > 12345678901
> >
> > > 0x12345678
> > > 0x12345678\n
> > just these 2 are what I had planned to allow after this email thread.
> >
> > > 0x123456789
> > >
> > > Maybe it's okay to be a little relaxed about this, and trust the caller
> > > to pass in data that makes sense.
> > yeah but is it worth the effort?
>
> Checking for exactly those two forms really is a lot of effort. You
> have to make sure the first two characters are "0x" or "0X", you have
> to check that each of the next eight characters is a valid hex digit,
> and you have to verify that the 11th character, if present, is a
> newline.
>
> If you can get results that are good enough just by calling
> strict_strtoul() without all these checks, it's probably worthwhile.
>
I just don't want any buffer overrun bugs in code I'm writing.
I like the attached thank you for all the really useful input.
--mark
Signed-off-by: mark gross <markgross@thegnar.org>
>From df199e491c750c529abcfb0e2256f508f1afd061 Mon Sep 17 00:00:00 2001
From: mark gross <markgross@thegnar.org>
Date: Sun, 6 Mar 2011 05:45:44 -0800
Subject: [PATCH] correct PM QOS's user mode interface to work with ascii input per
what is in the kernel docs. Writing a string to the ABI from user mode
comes in 2 flavors. one with and one without a '\n' at the end. this
change accepts both.
echo 0x12345678 > /dev/cpu_dma_latency
and
echo -n 0x12345678 > /dev/cpu_dma_latency
now both work.
---
kernel/pm_qos_params.c | 15 ++++++++-------
1 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/kernel/pm_qos_params.c b/kernel/pm_qos_params.c
index aeaa7f8..b315446 100644
--- a/kernel/pm_qos_params.c
+++ b/kernel/pm_qos_params.c
@@ -40,6 +40,7 @@
#include <linux/string.h>
#include <linux/platform_device.h>
#include <linux/init.h>
+#include <linux/kernel.h>
#include <linux/uaccess.h>
@@ -387,15 +388,15 @@ static ssize_t pm_qos_power_write(struct file *filp, const char __user *buf,
if (count == sizeof(s32)) {
if (copy_from_user(&value, buf, sizeof(s32)))
return -EFAULT;
- } else if (count == 11) { /* len('0x12345678/0') */
- if (copy_from_user(ascii_value, buf, 11))
+ } else if (count == 10 || count == 11) { /* '0x12345678' or
+ '0x12345678/n'*/
+ ascii_value[count] = 0;
+ if (copy_from_user(ascii_value, buf, count))
return -EFAULT;
- if (strlen(ascii_value) != 10)
+ if ((x=strict_strtol(ascii_value, 16, &value)) != 0){
+ pr_debug("%s, 0x%x, 0x%x\n",ascii_value, value, x);
return -EINVAL;
- x = sscanf(ascii_value, "%x", &value);
- if (x != 1)
- return -EINVAL;
- pr_debug("%s, %d, 0x%x\n", ascii_value, x, value);
+ }
} else
return -EINVAL;
--
1.7.1
next prev parent reply other threads:[~2011-03-06 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 1:54 [PATCH] PM QoS: Allow parsing of ASCII values Simon Horman
2011-02-18 5:05 ` mark gross
2011-02-18 6:39 ` Simon Horman
2011-02-18 15:17 ` Alan Stern
2011-02-22 4:33 ` mark gross
2011-02-23 6:56 ` mark gross
2011-02-23 15:20 ` Alan Stern
2011-02-24 16:17 ` mark gross
2011-02-24 17:00 ` Alan Stern
2011-03-06 14:07 ` mark gross [this message]
2011-03-29 20:01 ` Rafael J. Wysocki
2011-03-30 3:59 ` mark gross
2011-03-30 7:11 ` Simon Horman
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=20110306140714.GA2438@gvim.org \
--to=markgross@thegnar.org \
--cc=error27@gmail.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=stern@rowland.harvard.edu \
/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