linux-kernel - linux-next: manual merge of the kunit-next tree with the uml 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]

Message-ID: <20250708181539.0e778563@canb.auug.org.au>
Date: Tue, 8 Jul 2025 18:15:39 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Shuah Khan <skhan@...uxfoundation.org>, Richard Weinberger
 <richard@....at>
Cc: Johannes Berg <johannes.berg@...el.com>, Linux Kernel Mailing List
 <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>, Marie Zhussupova <marievic@...gle.com>,
 Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Subject: linux-next: manual merge of the kunit-next tree with the uml tree

Hi all,

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

  lib/kunit/Kconfig

between commit:

  013c51446570 ("kunit: Enable PCI on UML without triggering WARN()")

from the uml tree and commit:

  5ac244b9cc8f ("kunit: Make default kunit_test timeout configurable via both a module parameter and a Kconfig option")

from the kunit-next 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 lib/kunit/Kconfig
index c8ca155521b2,c10ede4b1d22..000000000000
--- a/lib/kunit/Kconfig
+++ b/lib/kunit/Kconfig
@@@ -93,11 -93,17 +93,24 @@@ config KUNIT_AUTORUN_ENABLE
  	  In most cases this should be left as Y. Only if additional opt-in
  	  behavior is needed should this be set to N.
  
 +config KUNIT_UML_PCI
 +	bool "KUnit UML PCI Support"
 +	depends on UML
 +	select UML_PCI
 +	help
 +	  Enables the PCI subsystem on UML for use by KUnit tests.
 +
+ config KUNIT_DEFAULT_TIMEOUT
+ 	int "Default value of the timeout module parameter"
+ 	default 300
+ 	help
+ 	  Sets the default timeout, in seconds, for Kunit test cases. This value
+ 	  is further multiplied by a factor determined by the assigned speed
+ 	  setting: 1x for `DEFAULT`, 3x for `KUNIT_SPEED_SLOW`, and 12x for
+ 	  `KUNIT_SPEED_VERY_SLOW`. This allows slower tests on slower machines
+ 	  sufficient time to complete.
+ 
+ 	  If unsure, the default timeout of 300 seconds is suitable for most
+ 	  cases.
+ 
  endif # KUNIT

Content of type "application/pgp-signature" skipped