From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
ian.jackson@eu.citrix.com, stefano.stabellini@eu.citrix.com,
ian.campbell@citrix.com, wei.liu2@citrix.com
Cc: jgross@suse.com, xen-devel@lists.xen.org, roger.pau@citrix.com
Subject: Re: [PATCH v2 1/2] libxc: Don't write terminating NULL character to command string
Date: Tue, 5 Jan 2016 17:59:52 -0500 [thread overview]
Message-ID: <568C4AE8.1050302@oracle.com> (raw)
In-Reply-To: <568C46B8.6020204@citrix.com>
On 01/05/2016 05:42 PM, Andrew Cooper wrote:
> On 05/01/2016 22:26, Boris Ostrovsky wrote:
>> When copying boot command string for HVMlite guests we explicitly write
>> '\0' at MAX_GUEST_CMDLINE offset. Unless the string is close to
>> MAX_GUEST_CMDLINE in length this write will end up in the wrong place,
>> beyond the end of the mapped range.
>>
>> Instead we should test string's length early and error out if it is too
>> long.
>>
>> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> MAX_GUEST_CMDLINE is an arbitrary and incorrect restriction. It is
> sadly baked into the PV ABI, but I specifically want to avoid lumbering
> DMLite with the failings of PV.
>
> By the looks of it, the only bug is the use of MAX_GUEST_CMDLINE. The
> xc_map_foreign_range() call already accounts for sufficient space to
> store the string when mapping guest memory.
Yes, I was also thinking about dropping it but ended up keeping it
mostly because it didn't feel right to blindly use strcpy().
-boris
>
> I think you only need the 2nd hunk of this patch.
>
> ~Andrew
>
>> ---
>> tools/libxc/xc_dom_x86.c | 8 ++++++--
>> 1 files changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/tools/libxc/xc_dom_x86.c b/tools/libxc/xc_dom_x86.c
>> index 3960875..b696149 100644
>> --- a/tools/libxc/xc_dom_x86.c
>> +++ b/tools/libxc/xc_dom_x86.c
>> @@ -647,6 +647,11 @@ static int alloc_magic_pages_hvm(struct xc_dom_image *dom)
>> if ( dom->cmdline )
>> {
>> cmdline_size = ROUNDUP(strlen(dom->cmdline) + 1, 8);
>> + if ( cmdline_size > MAX_GUEST_CMDLINE )
>> + {
>> + DOMPRINTF("Boot command line is too long");
>> + goto error_out;
>> + }
>> start_info_size += cmdline_size;
>>
>> }
>> @@ -676,8 +681,7 @@ static int alloc_magic_pages_hvm(struct xc_dom_image *dom)
>>
>> if ( dom->cmdline )
>> {
>> - strncpy(cmdline, dom->cmdline, MAX_GUEST_CMDLINE);
>> - cmdline[MAX_GUEST_CMDLINE - 1] = '\0';
>> + strcpy(cmdline, dom->cmdline);
>> start_info->cmdline_paddr = (seg.pfn << PAGE_SHIFT) +
>> ((uintptr_t)cmdline - (uintptr_t)start_info);
>> }
next prev parent reply other threads:[~2016-01-05 22:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 22:26 [PATCH v2 0/2] HVMlite start_info initialization fixes Boris Ostrovsky
2016-01-05 22:26 ` [PATCH v2 1/2] libxc: Don't write terminating NULL character to command string Boris Ostrovsky
2016-01-05 22:42 ` Andrew Cooper
2016-01-05 22:59 ` Boris Ostrovsky [this message]
2016-01-05 23:01 ` Andrew Cooper
2016-01-06 16:44 ` Ian Campbell
2016-01-06 16:51 ` Andrew Cooper
2016-01-06 17:06 ` Ian Campbell
2016-01-05 22:26 ` [PATCH v2 2/2] libxc: Defer initialization of start_page for HVM guests Boris Ostrovsky
2016-01-06 15:58 ` Wei Liu
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=568C4AE8.1050302@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).