From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Jonathan Lundell <linux@lundell-bros.com>
Cc: Kevin Corry <kevcorry@us.ibm.com>,
viro@parcelfarce.linux.theplanet.co.uk,
Bodo Rzany <bodo@rzany.de>,
Linux kernel <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 13:20:58 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0305021316350.9743@chaos> (raw)
In-Reply-To: <p05210604bad8521898a8@[207.213.214.37]>
On Fri, 2 May 2003, Jonathan Lundell wrote:
> At 11:27am -0400 5/2/03, Richard B. Johnson wrote:
> >If your conversion chances the base to 0, you divide by 0 (not
> >good) and don't get a remainder. Actually procedure number()
> >protects against a base less than 2 or greater than 36 so you
> >just prevent conversion altogether.
>
> A bug in number(), looks like. (base = 0) is intended to let the
> input string determine the base (16 if 0x*, else 8 if 0* else 10).
> Like simple_strtol().
> --
No. number() is an internal helper function. The base is correctly
set before number() is called. The reported bug had nothing at
all to do with the internal variable, base. Instead it had to
do with not allowing a leading "0x" for hexadecimal numbers
as the standard allows (or has been interpreted to allow).
This is simply fixed by inspection of the string variable before
a conversion is attempted.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.
next prev parent reply other threads:[~2003-05-02 17:06 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
2003-05-02 15:27 ` Richard B. Johnson
2003-05-02 16:52 ` Jonathan Lundell
2003-05-02 17:20 ` Richard B. Johnson [this message]
[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=Pine.LNX.4.53.0305021316350.9743@chaos \
--to=root@chaos.analogic.com \
--cc=bodo@rzany.de \
--cc=kevcorry@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@lundell-bros.com \
--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®