From: Andrew Morton <akpm@linux-foundation.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add parse_integer() (replacement for simple_strto*())
Date: Thu, 9 Apr 2015 13:02:47 -0700 [thread overview]
Message-ID: <20150409130247.18f3133c58b5ebc11f0f64d8@linux-foundation.org> (raw)
In-Reply-To: <20150409152613.GA14850@p183.telecom.by>
On Thu, 9 Apr 2015 18:26:14 +0300 Alexey Dobriyan <adobriyan@gmail.com> wrote:
> kstrto*() and kstrto*_from_user() family of functions were added
> help with parsing one integer written as string to proc/sysfs/debugfs
> files and pass it elsewhere. But they have a limitation: string passed
> must end with \0 or \n\0. There are enough places where kstrto*()
> functions can't be used because of this limitation. Trivial example:
> parse "%u.%u".
>
> ...
>
> include/linux/kernel.h | 72 +++++++++++++++++++
> lib/Makefile | 1
> lib/kstrtox.c | 27 +------
> lib/parse-integer.c | 180 +++++++++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 257 insertions(+), 23 deletions(-)
That's a lot of code for something which is almost the same as
kstrtofoo().
Can we hack up _kstrtoull() to optionally provide the new behaviour?
We could use the top bit of `base' to select the behaviour. Something
like
--- a/lib/kstrtox.c~a
+++ a/lib/kstrtox.c
@@ -87,19 +87,23 @@ static int _kstrtoull(const char *s, uns
{
unsigned long long _res;
unsigned int rv;
+ const char *cursor;
+ const unsigned int __base = base & 0x7fffffff;
- s = _parse_integer_fixup_radix(s, &base);
- rv = _parse_integer(s, base, &_res);
+ cursor = _parse_integer_fixup_radix(s, &__base);
+ rv = _parse_integer(cursor, __base, &_res);
if (rv & KSTRTOX_OVERFLOW)
return -ERANGE;
if (rv == 0)
return -EINVAL;
- s += rv;
- if (*s == '\n')
- s++;
- if (*s)
- return -EINVAL;
+ cursor += rv;
*res = _res;
+ if (base & 0x80000000)
+ return cursor - s;
+ if (*cursor == '\n')
+ cursor++;
+ if (*cursor)
+ return -EINVAL;
return 0;
}
then add a bunch of wrappers?
next prev parent reply other threads:[~2015-04-09 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 15:26 Alexey Dobriyan
2015-04-09 15:28 ` Alexey Dobriyan
2015-04-09 20:02 ` Andrew Morton [this message]
2015-04-11 15:36 ` Alexey Dobriyan
2015-04-11 15:38 ` [PATCH 1/2] " Alexey Dobriyan
2015-04-11 15:43 ` [PATCH 2/2] parse_integer: rewrite kstrto*() Alexey Dobriyan
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=20150409130247.18f3133c58b5ebc11f0f64d8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.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 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®