From: Greg KH <gregkh@linuxfoundation.org>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: Sasha Levin <sashal@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Haimin Zhang <tcs_kernel@tencent.com>,
TCS Robot <tcs_robot@tencent.com>,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
x86@kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH MANUALSEL 4.19 1/2] KVM: x86: Handle SRCU initialization failure during page track init
Date: Wed, 12 Jun 2024 14:38:05 +0200 [thread overview]
Message-ID: <2024061239-tinfoil-cryptic-e638@gregkh> (raw)
In-Reply-To: <9acccdfe-b7d8-b59d-7b00-d5a266b84d36@huawei.com>
On Wed, May 29, 2024 at 04:29:32PM +0800, Zenghui Yu wrote:
> On 2021/10/6 19:23, Paolo Bonzini wrote:
> > On 06/10/21 13:12, Sasha Levin wrote:
> > > From: Haimin Zhang <tcs_kernel@tencent.com>
> > >
> > > [ Upstream commit eb7511bf9182292ef1df1082d23039e856d1ddfb ]
> > >
> > > Check the return of init_srcu_struct(), which can fail due to OOM, when
> > > initializing the page track mechanism. Lack of checking leads to a NULL
> > > pointer deref found by a modified syzkaller.
> > >
> > > Reported-by: TCS Robot <tcs_robot@tencent.com>
> > > Signed-off-by: Haimin Zhang <tcs_kernel@tencent.com>
> > > Message-Id: <1630636626-12262-1-git-send-email-tcs_kernel@tencent.com>
> > > [Move the call towards the beginning of kvm_arch_init_vm. - Paolo]
> > > Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> > > Signed-off-by: Sasha Levin <sashal@kernel.org>
> >
> > Acked-by: Paolo Bonzini <pbonzini@redhat.com>
>
> Sasha, will this patch be applied for 4.19?
>
> The same question for the 5.4 backport [*]. It looks like both of them
> are missed for unknown reasons.
>
> [*] https://lore.kernel.org/stable/20211006111250.264294-1-sashal@kernel.org
This was from 2021, quite a while ago.
Can you please send them in backported form if you feel they should be
applied?
thanks,
greg k-h
prev parent reply other threads:[~2024-06-12 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 11:12 [PATCH MANUALSEL 4.19 1/2] KVM: x86: Handle SRCU initialization failure during page track init Sasha Levin
2021-10-06 11:12 ` [PATCH MANUALSEL 4.19 2/2] ALSA: pcsp: Make hrtimer forwarding more robust Sasha Levin
2021-10-06 11:23 ` [PATCH MANUALSEL 4.19 1/2] KVM: x86: Handle SRCU initialization failure during page track init Paolo Bonzini
2024-05-29 8:29 ` Zenghui Yu
2024-06-12 12:38 ` Greg KH [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=2024061239-tinfoil-cryptic-e638@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tcs_kernel@tencent.com \
--cc=tcs_robot@tencent.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yuzenghui@huawei.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