From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux KVM <kvm@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>, Theodor Milkov <tm@del.bg>
Subject: Re: Fwd: Persistent rt_sigreturn segfaults on KVM VMs after upgrade to 5.15
Date: Fri, 19 May 2023 15:19:32 +0700 [thread overview]
Message-ID: <68577e7d-a8ea-a3b5-4289-436a55e57f41@gmail.com> (raw)
In-Reply-To: <ZGY9twXBuTWpliAB@google.com>
On 5/18/23 22:01, Sean Christopherson wrote:
> On Thu, May 18, 2023, Bagas Sanjaya wrote:
>> On 5/18/23 20:57, Bagas Sanjaya wrote:
>>> Hi,
>>>
>>> I notice a regression report on Bugzilla [1]. Quoting from it:
>>>
>>>> I'm experiencing sporadic but persistent segmentation faults on the KVM
>>>> VMs I manage. These faults began appearing after upgrading from Linux
>>>> Kernel 4.x to 5.15.59. I further upgraded to 5.15.91 and transitioned the
>>>> userspace from Debian 10 (buster) to Debian 11 (bullseye), yet the issues
>>>> persist. Notably, the libc has also changed in the process as seen in the
>>>> following error logs:
>
> Was the host or guest kernel upgraded? If the guest kernel was upgraded, it's
> unlikely, though still possible, that this is a KVM bug.
>
The reporter [1] said that this regression occurs on guest kernel.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217457#c3
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2023-05-19 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 13:57 Bagas Sanjaya
2023-05-18 14:00 ` Bagas Sanjaya
2023-05-18 15:01 ` Sean Christopherson
2023-05-19 8:19 ` Bagas Sanjaya [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=68577e7d-a8ea-a3b5-4289-436a55e57f41@gmail.com \
--to=bagasdotme@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=seanjc@google.com \
--cc=tm@del.bg \
/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
all inboxes | Powered by JetHome®