linux-kernel - Re: [PATCH 1/1] KVM: MMU: Fix VM entry failure and OOPS for shdaow page table

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 7 Jun 2022 23:38:48 +0000
From:   Sean Christopherson <seanjc@...gle.com>
To:     Yuan Yao <yuan.yao@...ux.intel.com>
Cc:     Yuan Yao <yuan.yao@...el.com>, kvm@...r.kernel.org,
        linux-kernel@...r.kernel.org, Paolo Bonzini <pbonzini@...hat.com>,
        Vitaly Kuznetsov <vkuznets@...hat.com>,
        Wanpeng Li <wanpengli@...cent.com>,
        Jim Mattson <jmattson@...gle.com>,
        Joerg Roedel <joro@...tes.org>, Kai Huang <kai.huang@...el.com>
Subject: Re: [PATCH 1/1] KVM: MMU: Fix VM entry failure and OOPS for shdaow
 page table

On Wed, Jun 08, 2022, Yuan Yao wrote:
> On Tue, Jun 07, 2022 at 02:58:57PM +0000, Sean Christopherson wrote:
> > Everything below here can be dropped as it's not relevant to the original bug.
> >
> > E.g. the entire trace can be trimmed to:
> 
> Ah, I thought that the original trace carries most information
> which maybe useful to other people. Let me trim them as you
> suggested in V2, thanks.

For bug reports, it's helpful to have the raw trace as the context is useful for
debug.  But for changelogs, the goal is only to document the failure signature,
e.g. so that reviewers understand what broke, users that encounter a similar splat
can find a possible fix, etc...