linux-kernel - linux-next: manual merge of the kvm-x86 tree with the loongarch, kvm-arm trees

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

Date:   Mon, 30 Oct 2023 13:11:27 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Sean Christopherson <seanjc@...gle.com>,
        Christoffer Dall <cdall@...columbia.edu>,
        Marc Zyngier <maz@...nel.org>,
        Huacai Chen <chenhuacai@...ngson.cn>
Cc:     Ackerley Tng <ackerleytng@...gle.com>,
        Chao Peng <chao.p.peng@...ux.intel.com>,
        Huacai Chen <chenhuacai@...nel.org>,
        Isaku Yamahata <isaku.yamahata@...el.com>,
        Jing Zhang <jingzhangos@...gle.com>,
        "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Michael Roth <michael.roth@....com>,
        Oliver Upton <oliver.upton@...ux.dev>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Tianrui Zhao <zhaotianrui@...ngson.cn>,
        Yu Zhang <yu.c.zhang@...ux.intel.com>
Subject: linux-next: manual merge of the kvm-x86 tree with the loongarch,
 kvm-arm trees

Hi all,

Today's linux-next merge of the kvm-x86 tree got a conflict in:

  include/uapi/linux/kvm.h

between commits:

  b37e6b680e3a ("LoongArch: KVM: Add kvm related header files")
  3f9cd0ca8484 ("KVM: arm64: Allow userspace to get the writable masks for feature ID registers")

from the loongarch, kvm-arm trees and commits:

  8e555bf388af ("KVM: Introduce KVM_SET_USER_MEMORY_REGION2")
  3291e34c9986 ("KVM: Add KVM_EXIT_MEMORY_FAULT exit to report faults to userspace")
  e82df88abb18 ("KVM: Introduce per-page memory attributes")
  fcbef1e5e5d2 ("KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory")
  7e63404f9cd5 ("KVM: x86: Add support for "protected VMs" that can utilize private memory")

from the kvm-x86 tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc include/uapi/linux/kvm.h
index 211b86de35ac,5b5820d19e71..000000000000
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@@ -264,7 -278,7 +278,8 @@@ struct kvm_xen_exit 
  #define KVM_EXIT_RISCV_SBI        35
  #define KVM_EXIT_RISCV_CSR        36
  #define KVM_EXIT_NOTIFY           37
 -#define KVM_EXIT_MEMORY_FAULT     38
 +#define KVM_EXIT_LOONGARCH_IOCSR  38
++#define KVM_EXIT_MEMORY_FAULT     39
  
  /* For KVM_EXIT_INTERNAL_ERROR */
  /* Emulate instruction failed. */
@@@ -1200,7 -1214,11 +1222,12 @@@ struct kvm_ppc_resize_hpt 
  #define KVM_CAP_COUNTER_OFFSET 227
  #define KVM_CAP_ARM_EAGER_SPLIT_CHUNK_SIZE 228
  #define KVM_CAP_ARM_SUPPORTED_BLOCK_SIZES 229
 -#define KVM_CAP_USER_MEMORY2 230
 -#define KVM_CAP_MEMORY_FAULT_INFO 231
 -#define KVM_CAP_MEMORY_ATTRIBUTES 232
 -#define KVM_CAP_GUEST_MEMFD 233
 -#define KVM_CAP_VM_TYPES 234
 +#define KVM_CAP_ARM_SUPPORTED_REG_MASK_RANGES 230
++#define KVM_CAP_USER_MEMORY2 231
++#define KVM_CAP_MEMORY_FAULT_INFO 232
++#define KVM_CAP_MEMORY_ATTRIBUTES 233
++#define KVM_CAP_GUEST_MEMFD 234
++#define KVM_CAP_VM_TYPES 235
  
  #ifdef KVM_CAP_IRQ_ROUTING
  

Content of type "application/pgp-signature" skipped