All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Ian Campbell <ian.campbell@citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xen.org, ian.jackson@eu.citrix.com,
	stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH] libxc: remove most of tools/libxc/xc_dom_compat_linux.c
Date: Mon, 19 Oct 2015 12:36:51 +0200	[thread overview]
Message-ID: <5624C7C3.2030007@suse.com> (raw)
In-Reply-To: <1444137461.5302.167.camel@citrix.com>

On 10/06/2015 03:17 PM, Ian Campbell wrote:
> On Tue, 2015-10-06 at 14:06 +0100, Andrew Cooper wrote:
>> On 06/10/15 13:58, Wei Liu wrote:
>>> On Tue, Oct 06, 2015 at 01:52:16PM +0100, Andrew Cooper wrote:
>>>> On 06/10/15 12:35, Juergen Gross wrote:
>>>>> In tools/libxc/xc_dom_compat_linux.c only xc_linux_build() is
>>>>> currently
>>>>> being used by an in-tree component (qemu-xen). All other functions
>>>>> are
>>>>> superfluous wrappers of the domain builder which can be removed.
>>>>>
>>>>> Suggested-by: Ian Campbell <ian.campbell@citrix.com>
>>>>> Signed-off-by: Juergen Gross <jgross@suse.com>
>>>> Sorry, but NACK.  They are *not* superfluous.
>>>>
>>>> XenServer uses them; xc_dom_linux_build() is the only way to apply
>>>> XSA-25 size restrictions to PV kernels and initrds.
>>>>
>>> Could you explain a bit more about this? How could this particular
>>> function apply restrictions?
>>>
>>> Unfortunately XSA-25 is not on XSA page so I have no idea what that is.
>>>
>>> Wei.
>>
>> Older XSAs are listed on the wiki
>> http://wiki.xen.org/wiki/Security_Announcements
>>
>> XSA-25 introduced xc_dom_{kernel,ramdisk}_max_size() to set upper
>> decompression limits on the kernel and initrd.
>>
>> To use them, a struct xc_dom_image *dom is needed, which means the only
>> safe way of constructing PV domains is
>>
>> xc_dom_allocate()
>> xc_dom_kernel_max_size()
>> xc_dom_ramdisk_max_size()
>> xc_dom_linux_build()
>>
>> To have the decompression limits in place before decompression starts.
>
> No it isn't.
>
> xc_dom_linux_build is implemented in terms of the non-compat xc_dom_*
> functions, so it should be possible to do what you want with out using the
> compat wrapper.
>
> If there is some obscure reason this isn't the case then we should fix
> that, not carry around the compat options for ever as a workaround (fixes
> include but are not limited to promoting xc_dom_linux_build into a non
> -compat helper).

Any further comments?

Andrew, are you okay with Ian's statement?

Ian, does this mean you are Ack-ing the patch?


Juergen

  reply	other threads:[~2015-10-19 10:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 11:35 [PATCH] libxc: remove most of tools/libxc/xc_dom_compat_linux.c Juergen Gross
2015-10-06 12:52 ` Andrew Cooper
2015-10-06 12:58   ` Wei Liu
2015-10-06 13:06     ` Andrew Cooper
2015-10-06 13:17       ` Ian Campbell
2015-10-19 10:36         ` Juergen Gross [this message]
2015-10-22 15:22           ` Ian Jackson
2015-10-22 15:38             ` Ian Campbell
2015-10-23  7:15               ` Juergen Gross
2015-10-23  9:42                 ` Ian Campbell
2015-10-23  9:53                   ` Juergen Gross
2015-10-23 10:11                     ` Ian Campbell
2015-10-22 15:51           ` Andrew Cooper
2015-10-22 15:21         ` 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=5624C7C3.2030007@suse.com \
    --to=jgross@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.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 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.