[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 4/5] libvhost-user: prevent over-running max RAM slots
From: |
Stefan Hajnoczi |
Subject: |
Re: [PATCH v2 4/5] libvhost-user: prevent over-running max RAM slots |
Date: |
Mon, 10 Jan 2022 11:24:52 +0000 |
On Thu, Jan 06, 2022 at 06:47:35AM +0000, Raphael Norwitz wrote:
> When VHOST_USER_PROTOCOL_F_CONFIGURE_MEM_SLOTS support was added to
> libvhost-user, no guardrails were added to protect against QEMU
> attempting to hot-add too many RAM slots to a VM with a libvhost-user
> based backed attached.
>
> This change adds the missing error handling by introducing a check on
> the number of RAM slots the device has available before proceeding to
> process the VHOST_USER_ADD_MEM_REG message.
>
> Suggested-by: Stefan Hajnoczi <stefanha@redhat.com>
> Signed-off-by: Raphael Norwitz <raphael.norwitz@nutanix.com>
> ---
> subprojects/libvhost-user/libvhost-user.c | 5 +++++
> 1 file changed, 5 insertions(+)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
signature.asc
Description: PGP signature
- Re: [PATCH v2 2/5] libvhost-user: Add vu_add_mem_reg input validation, (continued)
- [PATCH v2 3/5] libvhost-user: Simplify VHOST_USER_REM_MEM_REG, Raphael Norwitz, 2022/01/06
- [PATCH v2 5/5] libvhost-user: handle removal of identical regions, Raphael Norwitz, 2022/01/06
- [PATCH v2 4/5] libvhost-user: prevent over-running max RAM slots, Raphael Norwitz, 2022/01/06
- Re: [PATCH v2 0/5] Clean up error handling in libvhost-user memory mapping, David Hildenbrand, 2022/01/10
- Re: [PATCH v2 0/5] Clean up error handling in libvhost-user memory mapping, Stefan Hajnoczi, 2022/01/10