linux-kernel - linux-next: manual merge of the vfs tree with the arm64 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>] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 17 Feb 2022 10:03:54 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Al Viro <viro@...IV.linux.org.uk>,
        Catalin Marinas <catalin.marinas@....com>,
        Will Deacon <will@...nel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: manual merge of the vfs tree with the arm64 tree

Hi all,

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

  arch/x86/um/Kconfig

between commit:

  b62a8486de3a ("elfcore: Replace CONFIG_{IA64, UML} checks with a new option")

from the arm64 tree and commit:

  6692531df62d ("uml/x86: use x86 load_unaligned_zeropad()")

from the vfs 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 arch/x86/um/Kconfig
index ead7e5b3a975,4eb47d3ba625..000000000000
--- a/arch/x86/um/Kconfig
+++ b/arch/x86/um/Kconfig
@@@ -8,7 -8,7 +8,8 @@@ endmen
  
  config UML_X86
  	def_bool y
 +	select ARCH_BINFMT_ELF_EXTRA_PHDRS if X86_32
+ 	select DCACHE_WORD_ACCESS
  
  config 64BIT
  	bool "64-bit kernel" if "$(SUBARCH)" = "x86"

Content of type "application/pgp-signature" skipped