linux-kernel - linux-next: manual merge of the kvm tree with the kvm-fixes tree

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]

Message-ID: <20190218142749.04daecaa@canb.auug.org.au>
Date:   Mon, 18 Feb 2019 14:27:49 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Paolo Bonzini <pbonzini@...hat.com>,
        Radim Krčmář <rkrcmar@...hat.com>,
        KVM <kvm@...r.kernel.org>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Luwei Kang <luwei.kang@...el.com>
Subject: linux-next: manual merge of the kvm tree with the kvm-fixes tree

Hi all,

Today's linux-next merge of the kvm tree got conflicts in:

  arch/x86/kvm/vmx/vmx.c
  arch/x86/kvm/vmx/vmx.h

between commit:

  c112b5f50232 ("KVM: x86: Recompute PID.ON when clearing PID.SN")

from the kvm-fixes tree and commit:

  abd2fb15a57e ("KVM: x86: Sync the pending Posted-Interrupts")

from the kvm tree.

These 2 commits are very similar so I just used the latter version of
the comflicting bits.

I fixed it up (see above) 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

Content of type "application/pgp-signature" skipped