From: Roland Dreier <roland@digitalvampire.org>
To: Michal Jaegermann <michal@harddata.com>
Cc: torvalds@transmeta.com, marcelo@conectiva.com.br,
alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix two bugs in lib/vsprintf.c
Date: 15 Jan 2002 16:54:57 -0800 [thread overview]
Message-ID: <876663ru72.fsf@love-shack.home.digitalvampire.org> (raw)
In-Reply-To: <87advgrmnh.fsf@love-shack.home.digitalvampire.org> <20020115172010.A26769@mail.harddata.com>
In-Reply-To: Michal Jaegermann's message of "Tue, 15 Jan 2002 17:20:10 -0700"
>>>>> "Michal" == Michal Jaegermann <michal@harddata.com> writes:
Michal> On Tue, Jan 15, 2002 at 01:25:38AM -0800, Roland Dreier wrote:
Roland> The below patch fixes two bugs in lib/vsprintf.c's
Roland> implementation of vsscanf().
Michal> If we are looking at these things I have some gnawing
Michal> suspicions that a constant 0xFFFFFFFFUL at line 489 of
Michal> lib/vsprintf.c in this function:
int vsprintf(char *buf, const char *fmt, va_list args)
{
return vsnprintf(buf, 0xFFFFFFFFUL, fmt, args);
}
Michal> was really meant to be (size_t)(-1). It is not the same
Michal> if a platform is not 32 bits. Roland, what do you think?
You are probably right, although I can't see it making much practical
difference (unlike the bugs I fixed, which actually bit me :) Still,
it wouldn't hurt to fix it.
R.
--
Roland Dreier <roland@digitalvampire.org>
GPG Key fingerprint = A89F B5E9 C185 F34D BD50 4009 37E2 25CC E0EE FAC0
prev parent reply other threads:[~2002-01-16 0:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 9:25 Roland Dreier
2002-01-16 0:20 ` Michal Jaegermann
2002-01-16 0:54 ` Roland Dreier [this message]
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=876663ru72.fsf@love-shack.home.digitalvampire.org \
--to=roland@digitalvampire.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=michal@harddata.com \
--cc=torvalds@transmeta.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®