linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: boris.ostrovsky@oracle.com, sstabellini@kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] xen: remove size limit of privcmd-buf mapping interface
Date: Fri, 9 Nov 2018 08:03:17 +0100	[thread overview]
Message-ID: <e60dacf6-9674-8fd6-d93c-a412667c5d6f@suse.com> (raw)
In-Reply-To: <20181101123307.8424-1-jgross@suse.com>

Ping?

Jan's remark regarding de-privileged qemu is no issue as the hypercall
node is being closed by the de-privilege library function.


Juergen

On 01/11/2018 13:33, Juergen Gross wrote:
> Currently the size of hypercall buffers allocated via
> /dev/xen/hypercall is limited to a default of 64 memory pages. For live
> migration of guests this might be too small as the page dirty bitmask
> needs to be sized according to the size of the guest. This means
> migrating a 8GB sized guest is already exhausting the default buffer
> size for the dirty bitmap.
> 
> There is no sensible way to set a sane limit, so just remove it
> completely. The device node's usage is limited to root anyway, so there
> is no additional DOS scenario added by allowing unlimited buffers.
> 
> While at it make the error path for the -ENOMEM case a little bit
> cleaner by setting n_pages to the number of successfully allocated
> pages instead of the target size.
> 
> Fixes: c51b3c639e01f2 ("xen: add new hypercall buffer mapping device")
> Cc: <stable@vger.kernel.org> #4.18
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
>  drivers/xen/privcmd-buf.c | 22 ++++------------------
>  1 file changed, 4 insertions(+), 18 deletions(-)
> 
> diff --git a/drivers/xen/privcmd-buf.c b/drivers/xen/privcmd-buf.c
> index df1ed37c3269..de01a6d0059d 100644
> --- a/drivers/xen/privcmd-buf.c
> +++ b/drivers/xen/privcmd-buf.c
> @@ -21,15 +21,9 @@
>  
>  MODULE_LICENSE("GPL");
>  
> -static unsigned int limit = 64;
> -module_param(limit, uint, 0644);
> -MODULE_PARM_DESC(limit, "Maximum number of pages that may be allocated by "
> -			"the privcmd-buf device per open file");
> -
>  struct privcmd_buf_private {
>  	struct mutex lock;
>  	struct list_head list;
> -	unsigned int allocated;
>  };
>  
>  struct privcmd_buf_vma_private {
> @@ -60,13 +54,10 @@ static void privcmd_buf_vmapriv_free(struct privcmd_buf_vma_private *vma_priv)
>  {
>  	unsigned int i;
>  
> -	vma_priv->file_priv->allocated -= vma_priv->n_pages;
> -
>  	list_del(&vma_priv->list);
>  
>  	for (i = 0; i < vma_priv->n_pages; i++)
> -		if (vma_priv->pages[i])
> -			__free_page(vma_priv->pages[i]);
> +		__free_page(vma_priv->pages[i]);
>  
>  	kfree(vma_priv);
>  }
> @@ -146,8 +137,7 @@ static int privcmd_buf_mmap(struct file *file, struct vm_area_struct *vma)
>  	unsigned int i;
>  	int ret = 0;
>  
> -	if (!(vma->vm_flags & VM_SHARED) || count > limit ||
> -	    file_priv->allocated + count > limit)
> +	if (!(vma->vm_flags & VM_SHARED))
>  		return -EINVAL;
>  
>  	vma_priv = kzalloc(sizeof(*vma_priv) + count * sizeof(void *),
> @@ -155,19 +145,15 @@ static int privcmd_buf_mmap(struct file *file, struct vm_area_struct *vma)
>  	if (!vma_priv)
>  		return -ENOMEM;
>  
> -	vma_priv->n_pages = count;
> -	count = 0;
> -	for (i = 0; i < vma_priv->n_pages; i++) {
> +	for (i = 0; i < count; i++) {
>  		vma_priv->pages[i] = alloc_page(GFP_KERNEL | __GFP_ZERO);
>  		if (!vma_priv->pages[i])
>  			break;
> -		count++;
> +		vma_priv->n_pages++;
>  	}
>  
>  	mutex_lock(&file_priv->lock);
>  
> -	file_priv->allocated += count;
> -
>  	vma_priv->file_priv = file_priv;
>  	vma_priv->users = 1;
>  
> 


  parent reply	other threads:[~2018-11-09  7:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01 12:33 Juergen Gross
2018-11-01 14:18 ` [Xen-devel] " Jan Beulich
2018-11-01 14:23   ` Juergen Gross
2018-11-01 15:50     ` Jan Beulich
     [not found]     ` <5BDB20AB020000780014251B@suse.com>
2018-11-01 16:27       ` Juergen Gross
2018-11-02  7:26         ` Jan Beulich
2018-11-01 14:23   ` Andrew Cooper
2018-11-09  7:03 ` Juergen Gross [this message]
2018-11-09 14:23   ` Boris Ostrovsky

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=e60dacf6-9674-8fd6-d93c-a412667c5d6f@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sstabellini@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    --subject='Re: [PATCH] xen: remove size limit of privcmd-buf mapping interface' \
    /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

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).