From: Kevin Corry <kevcorry@us.ibm.com>
To: viro@parcelfarce.linux.theplanet.co.uk, Bodo Rzany <bodo@rzany.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is there small mistake in lib/vsprintf.c of kernel 2.4.20 ?
Date: Fri, 2 May 2003 10:03:33 -0500 [thread overview]
Message-ID: <200305021003.33638.kevcorry@us.ibm.com> (raw)
In-Reply-To: <20030502095018.GY10374@parcelfarce.linux.theplanet.co.uk>
On Friday 02 May 2003 04:50, viro@parcelfarce.linux.theplanet.co.uk wrote:
> On Fri, May 02, 2003 at 11:42:36AM +0200, Bodo Rzany wrote:
> > > IOW, %d _does_ mean base=10. base=0 is %i. That goes both for kernel
> > > and userland implementations of scanf family (and for any
> > > standard-compliant implementation, for that matter).
> >
> > As I can see, 'base=10' is used for all conversions except for '%x' and
> > '%o'. If '%i' or '%u' are given, base should be really set to 0, what is
> > not the case (it is fixed to 10 instead!).
>
> Sorry - in 2.4 it's really broken. What we should have:
> %d -> 10
> %i -> 0
> %o -> 8
> %u -> 10
> %x -> 16
> (note: %u is decimal-only; see manpage).
>
> Fix (2.4-only, 2.5 is OK as it is):
>
> --- S21-rc1/lib/vsprintf.c Fri Jul 12 11:25:33 2002
> +++ /tmp/vsprintf.c Fri May 2 05:46:07 2003
> @@ -616,8 +616,9 @@
> case 'X':
> base = 16;
> break;
> - case 'd':
> case 'i':
> + base = 0;
> + case 'd':
> is_sign = 1;
> case 'u':
> break;
In order to get the hex and octal scanning correct, the following patch
also needs to be applied. For example, trying to scan "fe" with "%x"
currently fails. This is the same change that was made in 2.5.
diff -Naur linux-2.4.20a/lib/vsprintf.c linux-2.4.20b/lib/vsprintf.c
--- linux-2.4.20a/lib/vsprintf.c 2003-04-28 12:04:44.000000000 -0500
+++ linux-2.4.20b/lib/vsprintf.c 2003-04-28 12:04:25.000000000 -0500
@@ -637,7 +637,11 @@
while (isspace(*str))
str++;
- if (!*str || !isdigit(*str))
+ if (!*str
+ || (base == 16 && !isxdigit(*str))
+ || (base == 10 && !isdigit(*str))
+ || (base == 8 && (!isdigit(*str) || *str > '7'))
+ || (base == 0 && !isdigit(*str)))
break;
switch(qualifier) {
--
Kevin Corry
kevcorry@us.ibm.com
http://evms.sourceforge.net/
next prev parent reply other threads:[~2003-05-02 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 9:06 Bodo Rzany
2003-05-02 9:08 ` viro
2003-05-02 9:42 ` Bodo Rzany
2003-05-02 9:50 ` viro
2003-05-02 15:03 ` Kevin Corry [this message]
2003-05-02 15:27 ` Richard B. Johnson
2003-05-02 16:52 ` Jonathan Lundell
2003-05-02 17:20 ` Richard B. Johnson
[not found] <BKEGKPICNAKILKJKMHCAKEBLCKAA.Riley@Williams.Name>
2003-05-02 17:15 ` Richard B. Johnson
2003-05-02 18:23 ` Kevin Corry
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=200305021003.33638.kevcorry@us.ibm.com \
--to=kevcorry@us.ibm.com \
--cc=bodo@rzany.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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®