From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
ian.campbell@citrix.com, ian.jackson@eu.citrix.com,
jbeulich@suse.com, keir@xen.org, tim@xen.org
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH v2] vsprintf: Make sure argument to %pX specifier is valid
Date: Thu, 12 Feb 2015 10:01:52 -0500 [thread overview]
Message-ID: <54DCC060.8040208@oracle.com> (raw)
In-Reply-To: <54DC88D3.5080803@citrix.com>
On 02/12/2015 06:04 AM, Andrew Cooper wrote:
> On 11/02/15 20:58, Boris Ostrovsky wrote:
>> If invalid pointer (i.e. something smaller than HYPERVISOR_VIRT_START)
>> is passed for %*ph/%pv/%ps/%pS format specifiers then print "(NULL)"
>>
>> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>> ---
>> xen/common/vsprintf.c | 23 ++++++++++++++++-------
>> 1 files changed, 16 insertions(+), 7 deletions(-)
>>
>> v2:
>> * Print "(NULL)" instead of specifier-specific string
>> * Consider all addresses under HYPERVISOR_VIRT_START as invalid. (I think
>> this is true for both x86 and ARM but I don't have ARM platform to test).
>>
>>
>> diff --git a/xen/common/vsprintf.c b/xen/common/vsprintf.c
>> index 065cc42..b9542b5 100644
>> --- a/xen/common/vsprintf.c
>> +++ b/xen/common/vsprintf.c
>> @@ -270,6 +270,22 @@ static char *pointer(char *str, char *end, const char **fmt_ptr,
>> const char *fmt = *fmt_ptr, *s;
>>
>> /* Custom %p suffixes. See XEN_ROOT/docs/misc/printk-formats.txt */
>> +
>> + switch ( fmt[1] )
>> + {
>> + case 'h':
>> + case 's':
>> + case 'S':
>> + case 'v':
>> + ++*fmt_ptr;
>> + }
>> +
>> + if ( (unsigned long)arg < HYPERVISOR_VIRT_START )
>> + {
>> + char *s = "(NULL)";
>> + return string(str, end, s, -1, -1, 0);
>> + }
>> +
>> switch ( fmt[1] )
> This wont function, as you have inverted the increment of *fmt_ptr and
> check of fmt[1].
fmt value doesn't change, it is stashed at the top of the routine.
(What *is* wrong in the above code is the fact that the arg test is done
outside the switch. It should be part of the four case statements,
otherwise we will print plain %p arguments as "NULL").
>
> "(NULL)" is inappropriate for non-null pointers less than VIRT_START.
Yes, I thought about it after I sent it. "(invalid)"?
>
> Given the VIRT check, I would just put the entire switch statement
> inside an "if ( (unsigned long)arg < HYPERVISOR_VIRT_START )" block and
> let it fall through to the plain number case for a bogus pointer.
Not sure I understand what you are suggesting here, sorry.
-boris
>
> ~Andrew
>
>> {
>> case 'h': /* Raw buffer as hex string. */
>> @@ -277,9 +293,6 @@ static char *pointer(char *str, char *end, const char **fmt_ptr,
>> const uint8_t *hex_buffer = arg;
>> unsigned int i;
>>
>> - /* Consumed 'h' from the format string. */
>> - ++*fmt_ptr;
>> -
>> /* Bound user count from %* to between 0 and 64 bytes. */
>> if ( field_width <= 0 )
>> return str;
>> @@ -306,9 +319,6 @@ static char *pointer(char *str, char *end, const char **fmt_ptr,
>> unsigned long sym_size, sym_offset;
>> char namebuf[KSYM_NAME_LEN+1];
>>
>> - /* Advance parents fmt string, as we have consumed 's' or 'S' */
>> - ++*fmt_ptr;
>> -
>> s = symbols_lookup((unsigned long)arg, &sym_size, &sym_offset, namebuf);
>>
>> /* If the symbol is not found, fall back to printing the address */
>> @@ -335,7 +345,6 @@ static char *pointer(char *str, char *end, const char **fmt_ptr,
>> {
>> const struct vcpu *v = arg;
>>
>> - ++*fmt_ptr;
>> if ( str < end )
>> *str = 'd';
>> str = number(str + 1, end, v->domain->domain_id, 10, -1, -1, 0);
next prev parent reply other threads:[~2015-02-12 15:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 20:58 [PATCH v2] vsprintf: Make sure argument to %pX specifier is valid Boris Ostrovsky
2015-02-12 11:04 ` Andrew Cooper
2015-02-12 15:01 ` Boris Ostrovsky [this message]
2015-02-12 15:21 ` Andrew Cooper
2015-02-12 15:38 ` Boris Ostrovsky
2015-02-12 15:48 ` Andrew Cooper
2015-02-12 16:33 ` Boris Ostrovsky
2015-02-12 16:41 ` Boris Ostrovsky
2015-02-12 16:50 ` Andrew Cooper
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=54DCC060.8040208@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--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.