diff for duplicates of <ZOO782YGRY0YMuPu@google.com> diff --git a/a/content_digest b/N1/content_digest index 0ba42ea..a14cf48 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,9 +1,48 @@ "ref\0ZNvaJ3igvcvTZ/8k@google.com\0" "ref\0diqzzg2ktiao.fsf@ackerleytng-ctop.c.googlers.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Mon, 21 Aug 2023 12:33:07 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Ackerley Tng <ackerleytng@google.com>\0" + "Cc\0pbonzini@redhat.com" + maz@kernel.org + oliver.upton@linux.dev + chenhuacai@kernel.org + mpe@ellerman.id.au + anup@brainfault.org + paul.walmsley@sifive.com + palmer@dabbelt.com + aou@eecs.berkeley.edu + willy@infradead.org + akpm@linux-foundation.org + paul@paul-moore.com + jmorris@namei.org + serge@hallyn.com + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + kvmarm@lists.linux.dev + linux-mips@vger.kernel.org + linuxppc-dev@lists.ozlabs.org + kvm-riscv@lists.infradead.org + linux-riscv@lists.infradead.org + linux-fsdevel@vger.kernel.org + linux-mm@kvack.org + linux-security-module@vger.kernel.org + linux-kernel@vger.kernel.org + chao.p.peng@linux.intel.com + tabba@google.com + jarkko@kernel.org + yu.c.zhang@linux.intel.com + vannapurve@google.com + mail@maciej.szmigiero.name + vbabka@suse.cz + david@redhat.com + qperret@google.com + michael.roth@amd.com + wei.w.wang@intel.com + liam.merwick@oracle.com + isaku.yamahata@gmail.com + " kirill.shutemov@linux.intel.com\0" "\00:1\0" "b\0" "On Mon, Aug 21, 2023, Ackerley Tng wrote:\n" @@ -110,4 +149,4 @@ "struct kvm, with a different ASID/HKID, and get a false negative on the rebinding\n" check. -f4da9013c66ef1ea2cdf70d35c552730a3b0d195d9c5807a63bec4c47af5049a +08a9cb23e796362004c9319d474323120109742415055d37b31d0db68f01f61b
diff --git a/a/1.txt b/N2/1.txt index 21b3451..fc4c21b 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -101,3 +101,8 @@ solution, because it couldn't guard against KVM reusing a pointer. E.g. if a struct kvm was unbound and then freed, KVM could reuse the same memory for a new struct kvm, with a different ASID/HKID, and get a false negative on the rebinding check. + +_______________________________________________ +linux-riscv mailing list +linux-riscv@lists.infradead.org +http://lists.infradead.org/mailman/listinfo/linux-riscv diff --git a/a/content_digest b/N2/content_digest index 0ba42ea..4f09e9b 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,9 +1,48 @@ "ref\0ZNvaJ3igvcvTZ/8k@google.com\0" "ref\0diqzzg2ktiao.fsf@ackerleytng-ctop.c.googlers.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Mon, 21 Aug 2023 12:33:07 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Ackerley Tng <ackerleytng@google.com>\0" + "Cc\0pbonzini@redhat.com" + maz@kernel.org + oliver.upton@linux.dev + chenhuacai@kernel.org + mpe@ellerman.id.au + anup@brainfault.org + paul.walmsley@sifive.com + palmer@dabbelt.com + aou@eecs.berkeley.edu + willy@infradead.org + akpm@linux-foundation.org + paul@paul-moore.com + jmorris@namei.org + serge@hallyn.com + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + kvmarm@lists.linux.dev + linux-mips@vger.kernel.org + linuxppc-dev@lists.ozlabs.org + kvm-riscv@lists.infradead.org + linux-riscv@lists.infradead.org + linux-fsdevel@vger.kernel.org + linux-mm@kvack.org + linux-security-module@vger.kernel.org + linux-kernel@vger.kernel.org + chao.p.peng@linux.intel.com + tabba@google.com + jarkko@kernel.org + yu.c.zhang@linux.intel.com + vannapurve@google.com + mail@maciej.szmigiero.name + vbabka@suse.cz + david@redhat.com + qperret@google.com + michael.roth@amd.com + wei.w.wang@intel.com + liam.merwick@oracle.com + isaku.yamahata@gmail.com + " kirill.shutemov@linux.intel.com\0" "\00:1\0" "b\0" "On Mon, Aug 21, 2023, Ackerley Tng wrote:\n" @@ -108,6 +147,11 @@ "solution, because it couldn't guard against KVM reusing a pointer. E.g. if a\n" "struct kvm was unbound and then freed, KVM could reuse the same memory for a new\n" "struct kvm, with a different ASID/HKID, and get a false negative on the rebinding\n" - check. + "check.\n" + "\n" + "_______________________________________________\n" + "linux-riscv mailing list\n" + "linux-riscv@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-riscv -f4da9013c66ef1ea2cdf70d35c552730a3b0d195d9c5807a63bec4c47af5049a +6e6ac39e4d883f8cda7a229c6c5020ae12ff50db5aa2be0f57b4ca8ec2a57835
diff --git a/a/content_digest b/N3/content_digest index 0ba42ea..6821db2 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -1,9 +1,47 @@ "ref\0ZNvaJ3igvcvTZ/8k@google.com\0" "ref\0diqzzg2ktiao.fsf@ackerleytng-ctop.c.googlers.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Mon, 21 Aug 2023 12:33:07 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Ackerley Tng <ackerleytng@google.com>\0" + "Cc\0kvm@vger.kernel.org" + david@redhat.com + yu.c.zhang@linux.intel.com + linux-kernel@vger.kernel.org + linux-mm@kvack.org + chao.p.peng@linux.intel.com + linux-riscv@lists.infradead.org + isaku.yamahata@gmail.com + paul@paul-moore.com + maz@kernel.org + chenhuacai@kernel.org + jmorris@namei.org + willy@infradead.org + wei.w.wang@intel.com + tabba@google.com + jarkko@kernel.org + serge@hallyn.com + mail@maciej.szmigiero.name + aou@eecs.berkeley.edu + vbabka@suse.cz + michael.roth@amd.com + paul.walmsley@sifive.com + kvmarm@lists.linux.dev + linux-arm-kernel@lists.infradead.org + qperret@google.com + liam.merwick@oracle.com + linux-mips@vger.kernel.org + oliver.upton@linux.dev + linux-security-module@vger.kernel.org + palmer@dabbelt.com + kvm-riscv@lists.infradead.org + anup@brainfault.org + linux-fsdevel@vger.kernel.org + pbonzini@redhat.com + akpm@linux-foundation.org + vannapurve@google.com + linuxppc-dev@lists.ozlabs.org + " kirill.shutemov@linux.intel.com\0" "\00:1\0" "b\0" "On Mon, Aug 21, 2023, Ackerley Tng wrote:\n" @@ -110,4 +148,4 @@ "struct kvm, with a different ASID/HKID, and get a false negative on the rebinding\n" check. -f4da9013c66ef1ea2cdf70d35c552730a3b0d195d9c5807a63bec4c47af5049a +91396435288eef2e88ce57eaea735da590929c734800fc29b2a2f6489e5d55ff
diff --git a/a/1.txt b/N4/1.txt index 21b3451..9525755 100644 --- a/a/1.txt +++ b/N4/1.txt @@ -101,3 +101,8 @@ solution, because it couldn't guard against KVM reusing a pointer. E.g. if a struct kvm was unbound and then freed, KVM could reuse the same memory for a new struct kvm, with a different ASID/HKID, and get a false negative on the rebinding check. + +_______________________________________________ +linux-arm-kernel mailing list +linux-arm-kernel@lists.infradead.org +http://lists.infradead.org/mailman/listinfo/linux-arm-kernel diff --git a/a/content_digest b/N4/content_digest index 0ba42ea..a899f41 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -1,9 +1,48 @@ "ref\0ZNvaJ3igvcvTZ/8k@google.com\0" "ref\0diqzzg2ktiao.fsf@ackerleytng-ctop.c.googlers.com\0" "From\0Sean Christopherson <seanjc@google.com>\0" - "Subject\0[RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" + "Subject\0Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory\0" "Date\0Mon, 21 Aug 2023 12:33:07 -0700\0" - "To\0kvm-riscv@lists.infradead.org\0" + "To\0Ackerley Tng <ackerleytng@google.com>\0" + "Cc\0pbonzini@redhat.com" + maz@kernel.org + oliver.upton@linux.dev + chenhuacai@kernel.org + mpe@ellerman.id.au + anup@brainfault.org + paul.walmsley@sifive.com + palmer@dabbelt.com + aou@eecs.berkeley.edu + willy@infradead.org + akpm@linux-foundation.org + paul@paul-moore.com + jmorris@namei.org + serge@hallyn.com + kvm@vger.kernel.org + linux-arm-kernel@lists.infradead.org + kvmarm@lists.linux.dev + linux-mips@vger.kernel.org + linuxppc-dev@lists.ozlabs.org + kvm-riscv@lists.infradead.org + linux-riscv@lists.infradead.org + linux-fsdevel@vger.kernel.org + linux-mm@kvack.org + linux-security-module@vger.kernel.org + linux-kernel@vger.kernel.org + chao.p.peng@linux.intel.com + tabba@google.com + jarkko@kernel.org + yu.c.zhang@linux.intel.com + vannapurve@google.com + mail@maciej.szmigiero.name + vbabka@suse.cz + david@redhat.com + qperret@google.com + michael.roth@amd.com + wei.w.wang@intel.com + liam.merwick@oracle.com + isaku.yamahata@gmail.com + " kirill.shutemov@linux.intel.com\0" "\00:1\0" "b\0" "On Mon, Aug 21, 2023, Ackerley Tng wrote:\n" @@ -108,6 +147,11 @@ "solution, because it couldn't guard against KVM reusing a pointer. E.g. if a\n" "struct kvm was unbound and then freed, KVM could reuse the same memory for a new\n" "struct kvm, with a different ASID/HKID, and get a false negative on the rebinding\n" - check. + "check.\n" + "\n" + "_______________________________________________\n" + "linux-arm-kernel mailing list\n" + "linux-arm-kernel@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -f4da9013c66ef1ea2cdf70d35c552730a3b0d195d9c5807a63bec4c47af5049a +f22acb2bf23547aee0d12f95eecc874ad294362a65bfe6150aa0d29dadd22a6b
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.