diff options
author | Juergen Gross <jgross@suse.com> | 2018-11-01 13:33:07 +0100 |
---|---|---|
committer | Juergen Gross <jgross@suse.com> | 2018-11-09 16:38:34 +0100 |
commit | 3941552aec1e04d63999988a057ae09a1c56ebeb (patch) | |
tree | 3f9521547989145ad1ae2b36900845c9ac160d76 /fs/hfs/super.c | |
parent | d3132b3860f6cf35ff7609a76bbcdbb814bd027c (diff) | |
download | linux-3941552aec1e04d63999988a057ae09a1c56ebeb.tar.bz2 |
xen: remove size limit of privcmd-buf mapping interface
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>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Signed-off-by: Juergen Gross <jgross@suse.com>
Diffstat (limited to 'fs/hfs/super.c')
0 files changed, 0 insertions, 0 deletions