From: Kees Cook <kees@kernel.org>
To: Titouan Ameline de Cadeville <titouan.ameline@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/tests: exec: drop duplicate bprm_stack_limits test vectors
Date: Tue, 3 Feb 2026 17:36:24 -0800 [thread overview]
Message-ID: <202602031722.72C5EBFF15@keescook> (raw)
In-Reply-To: <20260203175950.43710-1-titouan.ameline@gmail.com>
On Tue, Feb 03, 2026 at 06:59:50PM +0100, Titouan Ameline de Cadeville wrote:
> Remove duplicate entries from the bprm_stack_limits KUnit test vector
> table. The duplicates do not add coverage and only increase test size.
Hm, yes, these are pointless duplicates. It makes me think I typo'd
something here.
> Signed-off-by: Titouan Ameline de Cadeville <titouan.ameline@gmail.com>
Regardless:
Fixes: 60371f43e56b ("exec: Add KUnit test for bprm_stack_limits()")
> ---
> fs/tests/exec_kunit.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/fs/tests/exec_kunit.c b/fs/tests/exec_kunit.c
> index 7c77d039680b..f412d1a0f6bb 100644
> --- a/fs/tests/exec_kunit.c
> +++ b/fs/tests/exec_kunit.c
> @@ -87,9 +87,6 @@ static const struct bprm_stack_limits_result bprm_stack_limits_results[] = {
> .argc = 0, .envc = ARG_MAX / sizeof(void *) - 1 },
> .expected_argmin = ULONG_MAX - sizeof(void *) },
> /* Raising rlim_stack / 4 to _STK_LIM / 4 * 3 will see more space. */
> - { { .p = ULONG_MAX, .rlim_stack.rlim_cur = 4 * (_STK_LIM / 4 * 3),
> - .argc = 0, .envc = 0 },
> - .expected_argmin = ULONG_MAX - (_STK_LIM / 4 * 3) + sizeof(void *) },
> { { .p = ULONG_MAX, .rlim_stack.rlim_cur = 4 * (_STK_LIM / 4 * 3),
> .argc = 0, .envc = 0 },
> .expected_argmin = ULONG_MAX - (_STK_LIM / 4 * 3) + sizeof(void *) },
Looking at the surrounding tests and trying to jog my memory, I think I
meant to have differing envc values here, but that turned out not to be
useful: I wanted to test the impact of rlim_stack.rlim_cur, not
argc/envc here.
> @@ -103,9 +100,6 @@ static const struct bprm_stack_limits_result bprm_stack_limits_results[] = {
> { { .p = ULONG_MAX, .rlim_stack.rlim_cur = 4 * _STK_LIM,
> .argc = 0, .envc = 0 },
> .expected_argmin = ULONG_MAX - (_STK_LIM / 4 * 3) + sizeof(void *) },
> - { { .p = ULONG_MAX, .rlim_stack.rlim_cur = 4 * _STK_LIM,
> - .argc = 0, .envc = 0 },
> - .expected_argmin = ULONG_MAX - (_STK_LIM / 4 * 3) + sizeof(void *) },
Same here.
Reviewed-by: Kees Cook <kees@kernel.org>
--
Kees Cook
next prev parent reply other threads:[~2026-02-04 1:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 17:59 Titouan Ameline de Cadeville
2026-02-04 1:36 ` Kees Cook [this message]
2026-02-04 1:41 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202602031722.72C5EBFF15@keescook \
--to=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=titouan.ameline@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox