From: Paolo Bonzini <pbonzini@redhat.com>
To: Salvatore Bonaccorso <carnil@debian.org>,
Stephen <stephenackerman16@gmail.com>
Cc: djwong@kernel.org, kvm@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, seanjc@google.com, rppt@kernel.org,
James.Bottomley@hansenpartnership.com, akpm@linux-foundation.org,
david@redhat.com, hagen@jauu.net
Subject: Re: kvm crash in 5.14.1?
Date: Wed, 13 Oct 2021 21:05:25 +0200 [thread overview]
Message-ID: <f430d53f-59cf-a658-a207-1f04adb32c56@redhat.com> (raw)
In-Reply-To: <YWcs3XRLdrvyRz31@eldamar.lan>
On 13/10/21 21:00, Salvatore Bonaccorso wrote:
> Hi,
>
> On Sat, Oct 09, 2021 at 12:00:39PM -0700, Stephen wrote:
>>> I'll try to report back if I see a crash; or in roughly a week if the
>> system seems to have stabilized.
>>
>> Just wanted to provide a follow-up here and say that I've run on both
>> v5.14.8 and v5.14.9 with this patch and everything seems to be good; no
>> further crashes or problems.
>
> In Debian we got a report as well related to this issue (cf.
> https://bugs.debian.org/996175). Do you know did the patch felt
> through the cracks?
Yeah, it's not a KVM patch so the mm maintainers didn't see it. I'll
handle it tomorrow.
Paolo
next prev parent reply other threads:[~2021-10-13 19:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 2:58 kvm crash in 5.14.1? Darrick J. Wong
2021-09-23 17:50 ` Stephen
2021-09-29 4:44 ` Stephen
2021-09-29 15:21 ` Sean Christopherson
2021-09-30 17:59 ` Darrick J. Wong
2021-10-04 16:54 ` Darrick J. Wong
2021-10-06 16:34 ` Darrick J. Wong
2021-10-03 5:47 ` Stephen
2021-10-09 19:00 ` Stephen
2021-10-13 19:00 ` Salvatore Bonaccorso
2021-10-13 19:05 ` Paolo Bonzini [this message]
2021-10-13 19:29 ` Sean Christopherson
2021-10-13 19:33 ` Salvatore Bonaccorso
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=f430d53f-59cf-a658-a207-1f04adb32c56@redhat.com \
--to=pbonzini@redhat.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=carnil@debian.org \
--cc=david@redhat.com \
--cc=djwong@kernel.org \
--cc=hagen@jauu.net \
--cc=kvm@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=seanjc@google.com \
--cc=stephenackerman16@gmail.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;
as well as URLs for NNTP newsgroup(s).