linux-kernel - linux-next: manual merge of the mm-nonmm-stable tree with the ftrace 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: <20220527152057.399bfc2b@canb.auug.org.au>
Date:   Fri, 27 May 2022 15:20:57 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Andrew Morton <akpm@...ux-foundation.org>,
        Steven Rostedt <rostedt@...dmis.org>
Cc:     David Disseldorp <ddiss@...e.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Masami Hiramatsu <mhiramat@...nel.org>
Subject: linux-next: manual merge of the mm-nonmm-stable tree with the
 ftrace tree

Hi all,

Today's linux-next merge of the mm-nonmm-stable tree got a conflict in:

  init/Kconfig

between commit:

  a2a9d67a26ec ("bootconfig: Support embedding a bootconfig file in kernel")

from the ftrace tree and commit:

  1274aea127b2 ("initramfs: add INITRAMFS_PRESERVE_MTIME Kconfig option")

from the mm-nonmm-stable 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 init/Kconfig
index 006e086f2724,90cb1ac936db..000000000000
--- a/init/Kconfig
+++ b/init/Kconfig
@@@ -1370,25 -1361,16 +1370,35 @@@ config BOOT_CONFI
  
  	  If unsure, say Y.
  
 +config BOOT_CONFIG_EMBED
 +	bool "Embed bootconfig file in the kernel"
 +	depends on BOOT_CONFIG
 +	help
 +	  Embed a bootconfig file given by BOOT_CONFIG_EMBED_FILE in the
 +	  kernel. Usually, the bootconfig file is loaded with the initrd
 +	  image. But if the system doesn't support initrd, this option will
 +	  help you by embedding a bootconfig file while building the kernel.
 +
 +	  If unsure, say N.
 +
 +config BOOT_CONFIG_EMBED_FILE
 +	string "Embedded bootconfig file path"
 +	depends on BOOT_CONFIG_EMBED
 +	help
 +	  Specify a bootconfig file which will be embedded to the kernel.
 +	  This bootconfig will be used if there is no initrd or no other
 +	  bootconfig in the initrd.
 +
+ config INITRAMFS_PRESERVE_MTIME
+ 	bool "Preserve cpio archive mtimes in initramfs"
+ 	default y
+ 	help
+ 	  Each entry in an initramfs cpio archive carries an mtime value. When
+ 	  enabled, extracted cpio items take this mtime, with directory mtime
+ 	  setting deferred until after creation of any child entries.
+ 
+ 	  If unsure, say Y.
+ 
  choice
  	prompt "Compiler optimization level"
  	default CC_OPTIMIZE_FOR_PERFORMANCE

Content of type "application/pgp-signature" skipped