From nobody Mon Feb 9 18:59:53 2026 Received: from smtp-42ac.mail.infomaniak.ch (smtp-42ac.mail.infomaniak.ch [84.16.66.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AADE33C485 for ; Fri, 1 Mar 2024 19:40:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=84.16.66.172 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1709322059; cv=none; b=u05TmLB3NyhHsCb72LoyixQMb1NoII+Llp6mZM++gktce/Qeu7pDyvEuftoyT0vQCrDYevFsbxa7DJBF7H2Fkd+eYbYCoxbz5fBmqYUX+dpkajRf60eABS2u9QSguf+4lRypmEb6uv3BoXXCzupx9Ag4lx+BjWu5vnpfWUUb5p0= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1709322059; c=relaxed/simple; bh=LH4Q4htqRz6rpUGaheNMvon3siFQfu5UoAMGUbGohVY=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=mZRN0HRJt4xy1jsHnkLrSMnxrqIqr5qgCxLStcQd71Jsa5XlI89OEcpF0qpu9BraOZEbuKD7HlR7TLlQbDqUcpyka24AJlTsaiQSwXt1qGByw0j6cqxV+azFyJBI8WiiB7EyJJ8odWmGWyFAGT+sqByv6CxZJRLB/+Qw/AOsCO4= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=digikod.net; spf=pass smtp.mailfrom=digikod.net; dkim=pass (1024-bit key) header.d=digikod.net header.i=@digikod.net header.b=ZOVbNPVy; arc=none smtp.client-ip=84.16.66.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=digikod.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=digikod.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=digikod.net header.i=@digikod.net header.b="ZOVbNPVy" Received: from smtp-4-0001.mail.infomaniak.ch (unknown [10.7.10.108]) by smtp-3-3000.mail.infomaniak.ch (Postfix) with ESMTPS id 4Tmdjy4TfvzMsbx9; Fri, 1 Mar 2024 20:40:54 +0100 (CET) Received: from unknown by smtp-4-0001.mail.infomaniak.ch (Postfix) with ESMTPA id 4Tmdjx66Bdzn46; Fri, 1 Mar 2024 20:40:53 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=digikod.net; s=20191114; t=1709322054; bh=LH4Q4htqRz6rpUGaheNMvon3siFQfu5UoAMGUbGohVY=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ZOVbNPVyXvbT7IZ4g7ed+SKnP3vu/Y+/7ya0hk099fnYnxqLOTAoUVEbSzNj18pyz IregfKv9+5PTt89Uf72nQVXpbMlZcXw/uyVZB4V+dZNkppV8/fGsOvBBnsOfY4ic8m I/9SuPTOTKMSACyhbIvAHXNMQRtLoHSgTEtjIFd8= From: =?UTF-8?q?Micka=C3=ABl=20Sala=C3=BCn?= To: Brendan Higgins , David Gow , Kees Cook , Rae Moar , Shuah Khan Cc: =?UTF-8?q?Micka=C3=ABl=20Sala=C3=BCn?= , Alan Maguire , Borislav Petkov , Dave Hansen , "H . Peter Anvin" , Ingo Molnar , James Morris , Luis Chamberlain , "Madhavan T . Venkataraman" , Marco Pagani , Paolo Bonzini , Sean Christopherson , Stephen Boyd , Thara Gopinath , Thomas Gleixner , Vitaly Kuznetsov , Wanpeng Li , Zahra Tarkhani , kvm@vger.kernel.org, linux-hardening@vger.kernel.org, linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, linux-um@lists.infradead.org, x86@kernel.org Subject: [PATCH v2 4/7] kunit: Handle test faults Date: Fri, 1 Mar 2024 20:40:34 +0100 Message-ID: <20240301194037.532117-5-mic@digikod.net> In-Reply-To: <20240301194037.532117-1-mic@digikod.net> References: <20240301194037.532117-1-mic@digikod.net> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Infomaniak-Routing: alpha Previously, when a kernel test thread crashed (e.g. NULL pointer dereference, general protection fault), the KUnit test hanged for 30 seconds and exited with a timeout error. Fix this issue by waiting on task_struct->vfork_done instead of the custom kunit_try_catch.try_completion, and track the execution state by initially setting try_result with -EFAULT and only setting it to 0 if the test passed. Fix kunit_generic_run_threadfn_adapter() signature by returning 0 instead of calling kthread_complete_and_exit(). Because thread's exit code is never checked, always set it to 0 to make it clear. Fix the -EINTR error message, which couldn't be reached until now. This is tested with a following patch. Cc: Brendan Higgins Cc: David Gow Cc: Rae Moar Cc: Shuah Khan Reviewed-by: Kees Cook Signed-off-by: Micka=C3=ABl Sala=C3=BCn Link: https://lore.kernel.org/r/20240301194037.532117-5-mic@digikod.net Reviewed-by: David Gow Tested-by: Rae Moar --- Changes since v1: * Added Kees's Reviewed-by. --- include/kunit/try-catch.h | 3 --- lib/kunit/try-catch.c | 14 +++++++------- 2 files changed, 7 insertions(+), 10 deletions(-) diff --git a/include/kunit/try-catch.h b/include/kunit/try-catch.h index c507dd43119d..7c966a1adbd3 100644 --- a/include/kunit/try-catch.h +++ b/include/kunit/try-catch.h @@ -14,13 +14,11 @@ =20 typedef void (*kunit_try_catch_func_t)(void *); =20 -struct completion; struct kunit; =20 /** * struct kunit_try_catch - provides a generic way to run code which might= fail. * @test: The test case that is currently being executed. - * @try_completion: Completion that the control thread waits on while test= runs. * @try_result: Contains any errno obtained while running test case. * @try: The function, the test case, to attempt to run. * @catch: The function called if @try bails out. @@ -46,7 +44,6 @@ struct kunit; struct kunit_try_catch { /* private: internal use only. */ struct kunit *test; - struct completion *try_completion; int try_result; kunit_try_catch_func_t try; kunit_try_catch_func_t catch; diff --git a/lib/kunit/try-catch.c b/lib/kunit/try-catch.c index cab8b24b5d5a..c6ee4db0b3bd 100644 --- a/lib/kunit/try-catch.c +++ b/lib/kunit/try-catch.c @@ -18,7 +18,7 @@ void __noreturn kunit_try_catch_throw(struct kunit_try_catch *try_catch) { try_catch->try_result =3D -EFAULT; - kthread_complete_and_exit(try_catch->try_completion, -EFAULT); + kthread_exit(0); } EXPORT_SYMBOL_GPL(kunit_try_catch_throw); =20 @@ -26,9 +26,12 @@ static int kunit_generic_run_threadfn_adapter(void *data) { struct kunit_try_catch *try_catch =3D data; =20 + try_catch->try_result =3D -EINTR; try_catch->try(try_catch->context); + if (try_catch->try_result =3D=3D -EINTR) + try_catch->try_result =3D 0; =20 - kthread_complete_and_exit(try_catch->try_completion, 0); + return 0; } =20 static unsigned long kunit_test_timeout(void) @@ -58,13 +61,11 @@ static unsigned long kunit_test_timeout(void) =20 void kunit_try_catch_run(struct kunit_try_catch *try_catch, void *context) { - DECLARE_COMPLETION_ONSTACK(try_completion); struct kunit *test =3D try_catch->test; struct task_struct *task_struct; int exit_code, time_remaining; =20 try_catch->context =3D context; - try_catch->try_completion =3D &try_completion; try_catch->try_result =3D 0; task_struct =3D kthread_create(kunit_generic_run_threadfn_adapter, try_catch, "kunit_try_catch_thread"); @@ -75,8 +76,7 @@ void kunit_try_catch_run(struct kunit_try_catch *try_catc= h, void *context) } get_task_struct(task_struct); wake_up_process(task_struct); - - time_remaining =3D wait_for_completion_timeout(&try_completion, + time_remaining =3D wait_for_completion_timeout(task_struct->vfork_done, kunit_test_timeout()); if (time_remaining =3D=3D 0) { try_catch->try_result =3D -ETIMEDOUT; @@ -92,7 +92,7 @@ void kunit_try_catch_run(struct kunit_try_catch *try_catc= h, void *context) if (exit_code =3D=3D -EFAULT) try_catch->try_result =3D 0; else if (exit_code =3D=3D -EINTR) - kunit_err(test, "wake_up_process() was never called\n"); + kunit_err(test, "try faulted\n"); else if (exit_code =3D=3D -ETIMEDOUT) kunit_err(test, "try timed out\n"); else if (exit_code) --=20 2.44.0