From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Tim Deegan <tim@xen.org>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH 1/4] common/vsprintf: Explicitly treat negative lengths as 'unlimited'
Date: Thu, 28 Nov 2013 16:48:37 +0000 [thread overview]
Message-ID: <529773E5.60309@citrix.com> (raw)
In-Reply-To: <1385656665-12551-2-git-send-email-tim@xen.org>
On 28/11/13 16:37, Tim Deegan wrote:
> The old code relied on implictly casting negative numbers to size_t
> making a very large limit, which was correct but non-obvious.
>
> Coverity CID 1128575
>
> Signed-off-by: Tim Deegan <tim@xen.org>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
This CID was introduced as a side effect of my %ps/%pS series, which was
basically code motion for this piece. The previous code was not exactly
fantastic.
> ---
> xen/common/vsprintf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/xen/common/vsprintf.c b/xen/common/vsprintf.c
> index 43dc392..68553bb 100644
> --- a/xen/common/vsprintf.c
> +++ b/xen/common/vsprintf.c
> @@ -239,7 +239,7 @@ static char *number(
> static char *string(char *str, char *end, const char *s,
> int field_width, int precision, int flags)
> {
> - int i, len = strnlen(s, precision);
> + int i, len = (precision < 0) ? strlen(s) : strnlen(s, precision);
>
> if (!(flags & LEFT)) {
> while (len < field_width--) {
next prev parent reply other threads:[~2013-11-28 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 16:37 [PATCH 0/4] xen: more Coverity-inspired tidying Tim Deegan
2013-11-28 16:37 ` [PATCH 1/4] common/vsprintf: Explicitly treat negative lengths as 'unlimited' Tim Deegan
2013-11-28 16:48 ` Andrew Cooper [this message]
2013-11-29 10:45 ` Ian Campbell
2013-11-28 16:37 ` [PATCH 2/4] x86/shadow: Drop shadow_mode_trap_reads() Tim Deegan
2013-11-28 16:37 ` [PATCH 3/4] x86/mem_sharing: drop unused variable Tim Deegan
2013-11-28 16:50 ` Andrew Cooper
2013-11-28 16:37 ` [PATCH 4/4] bitmaps/bitops: Clarify tests for small constant size Tim Deegan
2013-11-29 10:07 ` Jan Beulich
2013-11-29 10:37 ` Tim Deegan
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=529773E5.60309@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.