Re: [PATCH] Fix unsynchronized access to sev members through svm_register_enc_region

2021-01-27 Thread Sean Christopherson
On Tue, Jan 26, 2021, Tom Lendacky wrote: > On 1/26/21 12:54 PM, Peter Gonda wrote: > > sev_pin_memory assumes that callers hold the kvm->lock. This was true for > > all callers except svm_register_enc_region since it does not originate > > from svm_mem_enc_op. Also added lockdep annotation to help

Re: [PATCH] Fix unsynchronized access to sev members through svm_register_enc_region

2021-01-26 Thread Tom Lendacky
On 1/26/21 12:54 PM, Peter Gonda wrote: > sev_pin_memory assumes that callers hold the kvm->lock. This was true for > all callers except svm_register_enc_region since it does not originate > from svm_mem_enc_op. Also added lockdep annotation to help prevent > future regressions. I'm not exactly su

Re: [PATCH] Fix unsynchronized access to sev members through svm_register_enc_region

2021-01-26 Thread Sean Christopherson
On Tue, Jan 26, 2021, Peter Gonda wrote: > sev_pin_memory assumes that callers hold the kvm->lock. This was true for > all callers except svm_register_enc_region since it does not originate This doesn't actually state what change it being made, is only describes the problem. I'd also reword these

[PATCH] Fix unsynchronized access to sev members through svm_register_enc_region

2021-01-26 Thread Peter Gonda
sev_pin_memory assumes that callers hold the kvm->lock. This was true for all callers except svm_register_enc_region since it does not originate from svm_mem_enc_op. Also added lockdep annotation to help prevent future regressions. Tested: Booted SEV enabled VM on host. Cc: Thomas Gleixner Cc: I