From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Ramit Bhalla" <ramit.bhalla@wipro.com>
Cc: linux-kernel@vger.kernel.org, alan@redhat.com
Subject: Re: Bug in vsprintf.c - vsscanf()
Date: Tue, 2 Sep 2003 08:32:03 -0700 [thread overview]
Message-ID: <20030902083203.04df1d13.rddunlap@osdl.org> (raw)
In-Reply-To: <52C85426D39B314381D76DDD480EEE0CFC69DC@blr-m3-msg.wipro.com>
On Tue, 2 Sep 2003 10:29:07 +0530 "Ramit Bhalla" <ramit.bhalla@wipro.com> wrote:
| Oh sorry -
| It's the 2.4.19 kernel version.
In that case you can look at more recent kernel versions and
see that it's already fixed.
~Randy
| -----Original Message-----
| From: Randy.Dunlap [mailto:rddunlap@osdl.org]
| Sent: Monday, September 01, 2003 11:34 PM
| To: Ramit Bhalla
| Cc: linux-kernel@vger.kernel.org; alan@redhat.com
| Subject: Re: Bug in vsprintf.c - vsscanf()
|
|
| > Hi,
| >
| > There appears to be a bug in vsprintf.c
| > The function vsscanf (if I'm correct) is the kernel mode equivalent of user
| > mode sscanf. If one tries to read a hex string using the format "%x" it
| > returns an error if the read buffer contains any character other than 0-9.
| >
| > I believe the culprit lies on line 640 of vsprintf.c
| >
| > It should be "isxdigit" instead of "isdigit".
| >
| > Hope I'm not missing anything here :)
|
| Like what kernel version...?
|
| If it's 2.4.x, is it recent?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Tue, 2 Sep 2003 10:29:07 +0530 "Ramit Bhalla" <ramit.bhalla@wipro.com> wrote:
| Oh sorry -
| It's the 2.4.19 kernel version.
In that case you can look at more recent kernel versions and
see that it's already fixed.
~Randy
| -----Original Message-----
| From: Randy.Dunlap [mailto:rddunlap@osdl.org]
| Sent: Monday, September 01, 2003 11:34 PM
| To: Ramit Bhalla
| Cc: linux-kernel@vger.kernel.org; alan@redhat.com
| Subject: Re: Bug in vsprintf.c - vsscanf()
|
|
| > Hi,
| >
| > There appears to be a bug in vsprintf.c
| > The function vsscanf (if I'm correct) is the kernel mode equivalent of user
| > mode sscanf. If one tries to read a hex string using the format "%x" it
| > returns an error if the read buffer contains any character other than 0-9.
| >
| > I believe the culprit lies on line 640 of vsprintf.c
| >
| > It should be "isxdigit" instead of "isdigit".
| >
| > Hope I'm not missing anything here :)
|
| Like what kernel version...?
|
| If it's 2.4.x, is it recent?
next prev parent reply other threads:[~2003-09-02 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 4:59 Ramit Bhalla
2003-09-02 15:32 ` Randy.Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-01 16:14 Ramit Bhalla
2003-09-01 18:03 ` Randy.Dunlap
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=20030902083203.04df1d13.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ramit.bhalla@wipro.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®