From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, linuxppc-dev@lists.ozlabs.org
Cc: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH kernel] KVM: PPC: Book3S: Suppress warnings when allocating too big memory slots
Date: Wed, 15 Dec 2021 11:40:13 +1100 [thread overview]
Message-ID: <163952881326.928111.10777487820265480047.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20210901084512.1658628-1-aik@ozlabs.ru>
On Wed, 1 Sep 2021 18:45:12 +1000, Alexey Kardashevskiy wrote:
> The userspace can trigger "vmalloc size %lu allocation failure: exceeds
> total pages" via the KVM_SET_USER_MEMORY_REGION ioctl.
>
> This silences the warning by checking the limit before calling vzalloc()
> and returns ENOMEM if failed.
>
> This does not call underlying valloc helpers as __vmalloc_node() is only
> exported when CONFIG_TEST_VMALLOC_MODULE and __vmalloc_node_range() is not
> exported at all.
>
> [...]
Applied to powerpc/next.
[1/1] KVM: PPC: Book3S: Suppress warnings when allocating too big memory slots
https://git.kernel.org/powerpc/c/511d25d6b789fffcb20a3eb71899cf974a31bd9d
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, linuxppc-dev@lists.ozlabs.org
Cc: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH kernel] KVM: PPC: Book3S: Suppress warnings when allocating too big memory slots
Date: Wed, 15 Dec 2021 00:40:13 +0000 [thread overview]
Message-ID: <163952881326.928111.10777487820265480047.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20210901084512.1658628-1-aik@ozlabs.ru>
On Wed, 1 Sep 2021 18:45:12 +1000, Alexey Kardashevskiy wrote:
> The userspace can trigger "vmalloc size %lu allocation failure: exceeds
> total pages" via the KVM_SET_USER_MEMORY_REGION ioctl.
>
> This silences the warning by checking the limit before calling vzalloc()
> and returns ENOMEM if failed.
>
> This does not call underlying valloc helpers as __vmalloc_node() is only
> exported when CONFIG_TEST_VMALLOC_MODULE and __vmalloc_node_range() is not
> exported at all.
>
> [...]
Applied to powerpc/next.
[1/1] KVM: PPC: Book3S: Suppress warnings when allocating too big memory slots
https://git.kernel.org/powerpc/c/511d25d6b789fffcb20a3eb71899cf974a31bd9d
cheers
next prev parent reply other threads:[~2021-12-15 0:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 8:45 [PATCH kernel] KVM: PPC: Book3S: Suppress warnings when allocating too big memory slots Alexey Kardashevskiy
2021-09-01 8:45 ` Alexey Kardashevskiy
2021-09-01 14:59 ` Fabiano Rosas
2021-09-01 14:59 ` Fabiano Rosas
2021-09-02 4:25 ` Alexey Kardashevskiy
2021-09-02 4:25 ` Alexey Kardashevskiy
2021-09-02 13:08 ` Fabiano Rosas
2021-09-02 13:08 ` Fabiano Rosas
2021-09-02 13:23 ` David Laight
2021-09-02 13:23 ` David Laight
2021-12-15 0:40 ` Michael Ellerman [this message]
2021-12-15 0:40 ` Michael Ellerman
2021-09-01 8:45 [PATCH kernel] KVM: PPC: Book3S: Suppress failed alloc warning in H_COPY_TOFROM_GUEST Alexey Kardashevskiy
2021-09-01 8:45 ` Alexey Kardashevskiy
2021-09-01 14:45 ` Fabiano Rosas
2021-09-01 14:45 ` Fabiano Rosas
2021-12-15 0:40 ` Michael Ellerman
2021-12-15 0:40 ` Michael Ellerman
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=163952881326.928111.10777487820265480047.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=aik@ozlabs.ru \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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.