netdev - Re: [PATCH v2 RESEND] ptp: kvm: Use decrypted memory in confidential guest on x86

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] [day] [month] [year] [list]

Message-Id: <167911561836.25115.1462637997047748542.git-patchwork-notify@kernel.org>
Date:   Sat, 18 Mar 2023 05:00:18 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Jeremi Piotrowski <jpiotrowski@...ux.microsoft.com>
Cc:     linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        richardcochran@...il.com, hch@....de
Subject: Re: [PATCH v2 RESEND] ptp: kvm: Use decrypted memory in confidential
 guest on x86

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Wed,  8 Mar 2023 15:05:31 +0000 you wrote:
> KVM_HC_CLOCK_PAIRING currently fails inside SEV-SNP guests because the
> guest passes an address to static data to the host. In confidential
> computing the host can't access arbitrary guest memory so handling the
> hypercall runs into an "rmpfault". To make the hypercall work, the guest
> needs to explicitly mark the memory as decrypted. Do that in
> kvm_arch_ptp_init(), but retain the previous behavior for
> non-confidential guests to save us from having to allocate memory.
> 
> [...]

Here is the summary with links:
  - [v2,RESEND] ptp: kvm: Use decrypted memory in confidential guest on x86
    https://git.kernel.org/netdev/net-next/c/6365ba64b4db

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html