From: Paolo Bonzini <pbonzini@redhat.com>
To: "David Rientjes" <rientjes@google.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [patch] kvm: suppress KVM_SET_GSI_ROUTING allocation failure
Date: Tue, 13 Feb 2018 15:40:31 +0100 [thread overview]
Message-ID: <706b878f-3375-cf2b-c194-d348cb6d510b@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1802081334120.133173@chino.kir.corp.google.com>
On 08/02/2018 22:35, David Rientjes wrote:
> The KVM_SET_GSI_ROUTING ioctl does a vmalloc() of
> sizeof(struct kvm_irq_routing_entry) multiplied by a user-supplied value.
> This can be up to 4096 entries on architectures such as arm64 and s390
> (and the upper bound may be increased on s390 eventually).
>
> This can produce a vmalloc allocation failure warning:
>
> vmalloc: allocation failure: 0 bytes, mode:0x24000c2(GFP_KERNEL|__GFP_HIGHMEM)
> Call Trace:
> __dump_stack lib/dump_stack.c:15 [inline]
> dump_stack+0xf6/0x184 lib/dump_stack.c:51
> warn_alloc+0x208/0x230 mm/page_alloc.c:2930
> __vmalloc_node_range_memcg+0x510/0x670 mm/vmalloc.c:1711
> __vmalloc_node_memcg mm/vmalloc.c:1751 [inline]
> __vmalloc_node_memcg_flags mm/vmalloc.c:1788 [inline]
> vmalloc+0x69/0x70 mm/vmalloc.c:1803
> kvm_vm_ioctl+0x910/0x15e0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:4153
> vfs_ioctl fs/ioctl.c:44 [inline]
> do_vfs_ioctl+0x842/0xee0 fs/ioctl.c:611
> SYSC_ioctl fs/ioctl.c:626 [inline]
> SyS_ioctl+0x94/0xc0 fs/ioctl.c:617
> entry_SYSCALL_64_fastpath+0x12/0x17
>
> If the vmalloc address space is fully depleted, the ioctl can gracefully
> fail. Add __GFP_NOWARN to the allocation to suppress the warning.
>
> Signed-off-by: David Rientjes <rientjes@google.com>
Queued, thanks.
Paolo
> ---
> virt/kvm/kvm_main.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index 001085b611ad..d0352dd45b95 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -3063,7 +3063,8 @@ static long kvm_vm_ioctl(struct file *filp,
> goto out;
> if (routing.nr) {
> r = -ENOMEM;
> - entries = vmalloc(routing.nr * sizeof(*entries));
> + entries = __vmalloc(routing.nr * sizeof(*entries),
> + GFP_KERNEL | __GFP_NOWARN, PAGE_KERNEL);
> if (!entries)
> goto out;
> r = -EFAULT;
>
next prev parent reply other threads:[~2018-02-13 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 21:35 David Rientjes
2018-02-13 14:40 ` Paolo Bonzini [this message]
2018-02-13 14:48 ` Michal Hocko
2018-02-13 15:03 ` Paolo Bonzini
2018-02-13 15:44 ` Michal Hocko
2018-02-13 15:49 ` Paolo Bonzini
2018-02-13 15:58 ` Michal Hocko
2018-02-13 15:14 ` Christian Borntraeger
2018-02-13 15:17 ` Paolo Bonzini
2018-02-14 1:03 ` David Rientjes
2018-02-14 8:30 ` Christian Borntraeger
2018-02-14 10:10 ` Paolo Bonzini
2018-02-14 11:14 ` Christian Borntraeger
2018-02-14 11:32 ` Paolo Bonzini
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=706b878f-3375-cf2b-c194-d348cb6d510b@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=rkrcmar@redhat.com \
/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
all inboxes | Powered by JetHome®