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-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 15 Dec 2023 17:24:22 +0100
From: Greg Kroah-Hartman <>
Cc: Rae Moar <>,
	Brendan Higgins <>,
	Matti Vaittinen <>,
	Stephen Boyd <>,
	Shuah Khan <>,
	Jonathan Corbet <>, Kees Cook <>,
	Liam Girdwood <>,
	Mark Brown <>, Jaroslav Kysela <>,
	Takashi Iwai <>, Maxime Ripard <>,,,,,,
Subject: Re: [PATCH v4 1/5] kunit: Add APIs for managing devices

On Fri, Dec 15, 2023 at 03:39:08PM +0800, wrote:
> Tests for drivers often require a struct device to pass to other
> functions. While it's possible to create these with
> root_device_register(), or to use something like a platform device, this
> is both a misuse of those APIs, and can be difficult to clean up after,
> for example, a failed assertion.
> Add some KUnit-specific functions for registering and unregistering a
> struct device:
> - kunit_device_register()
> - kunit_device_register_with_driver()
> - kunit_device_unregister()
> These helpers allocate a on a 'kunit' bus which will either probe the
> driver passed in (kunit_device_register_with_driver), or will create a
> stub driver (kunit_device_register) which is cleaned up on test shutdown.
> Devices are automatically unregistered on test shutdown, but can be
> manually unregistered earlier with kunit_device_unregister() in order
> to, for example, test device release code.
> Reviewed-by: Matti Vaittinen <>
> Reviewed-by: Maxime Ripard <>
> Signed-off-by: David Gow <>

Nice work!

Reviewed-by: Greg Kroah-Hartman <>

Powered by blists - more mailing lists