diff for duplicates of <YZaeL5YztL3p1nLM@google.com>

diff --git a/a/1.txt b/N1/1.txt
index e70a1f6..d739a21 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,6 +1,6 @@
 On Thu, Nov 18, 2021, David Woodhouse wrote:
 > That leaves the one in TDP MMU handle_changed_spte_dirty_log() which
-> AFAICT can trigger the same crash seen by butt3rflyh4ck ? can't that
+> AFAICT can trigger the same crash seen by butt3rflyh4ck — can't that
 > happen from a thread where kvm_get_running_vcpu() is NULL too? For that
 > one I'm not sure.
 
@@ -20,3 +20,7 @@ On 03/12/19 20:01, Sean Christopherson wrote:
 > IMO, it's a unnecessary hack.  The proper change to ensure a valid vCPU is
 > seen by mark_page_dirty_in_ring() when there is a current vCPU is to
 > plumb the vCPU down through the various call stacks.
+_______________________________________________
+kvmarm mailing list
+kvmarm@lists.cs.columbia.edu
+https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
diff --git a/a/content_digest b/N1/content_digest
index f763e6a..8d7e38c 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -4,14 +4,39 @@
  "ref\04c48546b-eb4a-dff7-cc38-5df54f73f5d4@redhat.com\0"
  "ref\020b5952e76c54a3a5dfe5a898e3b835404ac6fb1.camel@infradead.org\0"
  "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0[PATCH v3 08/12] KVM: Propagate vcpu explicitly to mark_page_dirty_in_slot()\0"
+ "Subject\0Re: [PATCH v3 08/12] KVM: Propagate vcpu explicitly to mark_page_dirty_in_slot()\0"
  "Date\0Thu, 18 Nov 2021 18:40:47 +0000\0"
- "To\0kvm-riscv@lists.infradead.org\0"
+ "To\0David Woodhouse <dwmw2@infradead.org>\0"
+ "Cc\0Anup Patel <anup.patel@wdc.com>"
+  wanpengli @ tencent . com <wanpengli@tencent.com>
+  kvm <kvm@vger.kernel.org>
+  Benjamin Herrenschmidt <benh@kernel.crashing.org>
+  Joao Martins <joao.m.martins@oracle.com>
+  Will Deacon <will@kernel.org>
+  kvmarm@lists.cs.columbia.edu
+  linux-s390@vger.kernel.org
+  Michael Ellerman <mpe@ellerman.id.au>
+  joro @ 8bytes . org <joro@8bytes.org>
+  Huacai Chen <chenhuacai@kernel.org>
+  Christian Borntraeger <borntraeger@de.ibm.com>
+  Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
+  karahmed@amazon.com
+  Catalin Marinas <catalin.marinas@arm.com>
+  Boris Ostrovsky <boris.ostrovsky@oracle.com>
+  linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
+  jmattson @ google . com <jmattson@google.com>
+  mtosatti @ redhat . com <mtosatti@redhat.com>
+  linux-mips@vger.kernel.org
+  kvm-riscv@lists.infradead.org
+  Marc Zyngier <maz@kernel.org>
+  Paolo Bonzini <pbonzini@redhat.com>
+  vkuznets @ redhat . com <vkuznets@redhat.com>
+ " linuxppc-dev@lists.ozlabs.org\0"
  "\00:1\0"
  "b\0"
  "On Thu, Nov 18, 2021, David Woodhouse wrote:\n"
  "> That leaves the one in TDP MMU handle_changed_spte_dirty_log() which\n"
- "> AFAICT can trigger the same crash seen by butt3rflyh4ck ? can't that\n"
+ "> AFAICT can trigger the same crash seen by butt3rflyh4ck \342\200\224 can't that\n"
  "> happen from a thread where kvm_get_running_vcpu() is NULL too? For that\n"
  "> one I'm not sure.\n"
  "\n"
@@ -30,6 +55,10 @@
  "> In case it was clear, I strongly dislike adding kvm_get_running_vcpu().\n"
  "> IMO, it's a unnecessary hack.  The proper change to ensure a valid vCPU is\n"
  "> seen by mark_page_dirty_in_ring() when there is a current vCPU is to\n"
- > plumb the vCPU down through the various call stacks.
+ "> plumb the vCPU down through the various call stacks.\n"
+ "_______________________________________________\n"
+ "kvmarm mailing list\n"
+ "kvmarm@lists.cs.columbia.edu\n"
+ https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
 
-306b10ddf3b6af3dd5f08857818c7198f8139665dd45a99aae9f1cd9f684c93b
+d6d833ac600b7c56423d81efa8604ae9480f427d1bb8e0113145eaf5efabb078
