From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: oficerovas@altlinux.org, stable@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Michael Ellerman <mpe@ellerman.id.au>,
kovalev@altlinux.org, nickel@altlinux.org, dutyrok@altlinux.org
Subject: Re: [PATCH 0/2] kvm: fix kmalloc bug in kvm_arch_prepare_memory_region on 5.10 stable kernel
Date: Fri, 26 Jan 2024 16:51:20 -0800 [thread overview]
Message-ID: <2024012612-stubborn-sprain-870a@gregkh> (raw)
In-Reply-To: <CABgObfaoremaWjiOCFJey4EPMLt3MKbny+QuU8Gut18MxwVhCg@mail.gmail.com>
On Fri, Jan 26, 2024 at 07:04:51PM +0100, Paolo Bonzini wrote:
> On Fri, Jan 26, 2024 at 11:01 AM <oficerovas@altlinux.org> wrote:
> >
> > From: Alexander Ofitserov <oficerovas@altlinux.org>
> >
> > Syzkaller hit 'WARNING: kmalloc bug in kvm_arch_prepare_memory_region' bug.
> >
> > This bug is not a vulnerability and is reproduced only when running with root privileges
> > for stable 5.10 kernel.
> >
> > Bug fixed by backported commits in next two patches.
> > [PATCH 1/2] mm: vmalloc: introduce array allocation functions
> > [PATCH 2/2] KVM: use __vcalloc for very large allocations
>
> Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Thanks for the review, both now queued up.
greg k-h
prev parent reply other threads:[~2024-01-27 0:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 9:55 [PATCH 0/2] kvm: fix kmalloc bug in kvm_arch_prepare_memory_region on 5.10 stable kernel oficerovas
2024-01-26 9:55 ` [PATCH 1/2] mm: vmalloc: introduce array allocation functions oficerovas
2024-01-26 13:59 ` David Laight
2024-01-26 18:42 ` Paolo Bonzini
2024-01-27 0:50 ` Greg Kroah-Hartman
2024-01-26 9:55 ` [PATCH 2/2] KVM: use __vcalloc for very large allocations oficerovas
2024-01-26 18:04 ` [PATCH 0/2] kvm: fix kmalloc bug in kvm_arch_prepare_memory_region on 5.10 stable kernel Paolo Bonzini
2024-01-27 0:51 ` Greg Kroah-Hartman [this message]
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=2024012612-stubborn-sprain-870a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=dutyrok@altlinux.org \
--cc=kovalev@altlinux.org \
--cc=mpe@ellerman.id.au \
--cc=nickel@altlinux.org \
--cc=oficerovas@altlinux.org \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox