linux-kernel - Re: [PATCH v6 6/7] KVM: arm64: allow get exception information from userspace

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAMj-D2AuCqAgQBRAp2CSf24HsHWteNLigZAUEKK8oKL_SAmBNw@mail.gmail.com>
Date:   Wed, 27 Sep 2017 23:37:18 +0800
From:   gengdongjiu <gengdj.1984@...il.com>
To:     gengdongjiu <gengdongjiu@...wei.com>
Cc:     James Morse <james.morse@....com>, wangkefeng.wang@...wei.com,
        kvm@...r.kernel.org, david.daney@...ium.com,
        catalin.marinas@....com, Achin Gupta <Achin.Gupta@....com>,
        Tyler Baicar <tbaicar@...eaurora.org>, will.deacon@....com,
        linuxarm@...wei.com, robert.moore@...el.com, lv.zheng@...el.com,
        zjzhang@...eaurora.org, mingo@...nel.org, stefan@...lo-penguin.com,
        linux@...linux.org.uk, kvmarm@...ts.cs.columbia.edu,
        linux-acpi@...r.kernel.org, Huangshaoyu <huangshaoyu@...wei.com>,
        huangdaode@...ilicon.com, Borislav Petkov <bp@...e.de>,
        Dave.Martin@....com, Len Brown <lenb@...nel.org>,
        wuquanming <wuquanming@...wei.com>,
        Marc Zyngier <marc.zyngier@....com>,
        John Garry <john.garry@...wei.com>, kristina.martsenko@....com,
        cov@...eaurora.org, jonathan.cameron@...wei.com,
        zhengqiang10@...wei.com,
        arm-mail-list <linux-arm-kernel@...ts.infradead.org>,
        devel@...ica.org, Ard Biesheuvel <ard.biesheuvel@...aro.org>,
        linux-kernel@...r.kernel.org, wangzhou1@...ilicon.com,
        mst@...hat.com, Shiju Jose <shiju.jose@...wei.com>
Subject: Re: [PATCH v6 6/7] KVM: arm64: allow get exception information from userspace

>> What you may be seeing is some awkwardness with the change in the SError ESR
>> with v8.2. Previously the VSE mechanism injected an impdef SError, (but they
>> were all impdef so it didn't matter).
>> With VSESR_EL2 KVM has to specify one, and all-zeros is a bad choice as this
>> means 'classified as a RAS error ... unknown!'.
>>
>> I have a patch in the upcoming SError/RAS series that changes KVMs virtual-abort
>> code to specify an impdef ESR for this path.
> Before I remember Marc and you suggest me specify the an impdef ESR (set the vsesr_el2) in
> the userspace,

I pasted Marc's propose and your suggestion that set VSESR_EL2(specify
virtual SError syndrome) by the user space.
https://lkml.org/lkml/2017/3/20/441
https://lkml.org/lkml/2017/3/20/516


> now do you want to specify an impdef ESR in KVM instead of usrspace?
> if setting the vsesr_el2 in the KVM, whether user-space need to specify?
> May be we can combine the patches that specify an impdef ESR(set vsesr_el2) patch to one.
>